lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patches for issue #4814


From: James Lowe
Subject: Re: Patches for issue #4814
Date: Sat, 23 Jul 2016 12:32:28 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

Hello,

On 22/07/16 14:41, Guido Aulisi wrote:
Hello,
I made 2 patches for issue #4814 and for a FTBFS witch gcc 6 on Fedora 24.
These 2 patches seem to solve that problem for me.

Best regards
Guido Aulisi


_______________________________________________
lilypond-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Thanks I have added them to the tracker, so that they don't get lost.

As a matter of fact, I just upgraded to Fedora 24 last Tuesday and now am getting problems with just regular 'make' (I'd forgotten all about Federico's mail (and this tracker)).

Oh dear.

--snip--

make[1]: *** [out/dynamic-performer.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/home/james/lilypond-git/lily/lily-lexer.cc: In member function 'int Lily_lexer::lookup_keyword(const string&)': /home/james/lilypond-git/lily/lily-lexer.cc:185:28: warning: conversion to 'int' from 'vsize {aka long unsigned int}' may alter its value [-Wconversion]
   return keytable_->lookup (s.c_str ());
          ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
/home/james/lilypond-git/lily/score.cc: In member function 'scm_unused_struct* Score::book_rendering(Output_def*, Output_def*)': /home/james/lilypond-git/lily/score.cc:125:33: warning: conversion to 'int' from 'std::vector<Output_def*>::size_type {aka long unsigned int}' may alter its value [-Wconversion]
   int outdef_count = defs_.size ();
                      ~~~~~~~~~~~^~
make[1]: Leaving directory '/home/james/lilypond-git/build/lily'
/home/james/lilypond-git/stepmake/stepmake/generic-targets.make:6: recipe for target 'all' failed
make: *** [all] Error 2

--snip--

So I guess (hope) that these two patches will allow me to make again.

:)

I'll know very shortly.

--
--

James



reply via email to

[Prev in Thread] Current Thread [Next in Thread]