On Friday, July 10, 2015 12:28:53 AM you wrote: > Thomas Spuhler <[email protected]> writes: > > I am the packager of Lilypond for Mageia. > > Unfortunately, version 2.19.22 doesn't build, 2.19.21 did. > > Is there a new BuildRequirement for vers. 2.19.22? > > The bug I get is: > > cd ./out && > > /home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.22/scripts/build/out/run-and-check > > "/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.22/out/bin/lilypond > > --verbose > > /home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.22/ly/generate-documentation" > > "generate- > > documentation.log" > > > > Please check the logfile generate-documentation.log for errors > > > > GNUmakefile:295: recipe for target 'out/internals.texi' failed > > make[1]: *** [out/internals.texi] Error 1 > > > > The generate-documentation.log shows this: > > > > [/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.22/out/share/lilypond/current/ly/engraver- > > init.ly/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.22/out/share/lilypond/current/scm/li > > ly.scmBacktrace:> > > In ice-9/boot-9.scm: > > 157: 14 [catch #t #<catch-closure 2d660c0> ...] > > > > In unknown file: > > ?: 13 [apply-smob/1 #<catch-closure 2d660c0>] > > > > In ice-9/eval.scm: > > 411: 12 [eval # #] > > 432: 11 [eval # #] > > > > In srfi/srfi-1.scm: > > 619: 10 [for-each #<procedure 4375090 at ice-9/eval.scm:416:20 (a)> #] > > > > In ice-9/eval.scm: > ice-9/eval.scm is a file from GUILE 2.0. LilyPond requires compilation > with GUILE 1.8.8. LilyPond would not even have made it across the > configure stage with GUILE 2.0 without particular options and care, and > it never would have run. So I doubt that there is something new with > LilyPond that is causing a problem for you. Either this never worked in > this manner, or the person responsible for getting it to run previously > should immediately report for duty at LilyPond central since over _here_ > GUILE 2.0 is still an unsolved problem.
David, version 2.19.21 actually built. I haven't done any testing, but will. There is a strong push for Guile 2 from our community (lilypond being the last package still requiring? guile-1.8 So I need strong arguments for no using guile-2 such as the package is not working. -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
