2017-03-26 0:48 GMT+01:00 James <p...@gnu.org>: > Hello > > After 5099 was pushed I am now seeing problems with basic 'make'. > > --snip-- > > og level set to 287 > Relocation: is absolute: > argv0=/tmp/build-lilypond-autobuild/out/bin/lilypond > PATH=/tmp/build-lilypond-autobuild/out/bin (prepend) Setting PATH > to > /tmp/build-lilypond-autobuild/out/bin:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/james/.local/bin:/home/james/bin:/home/james/lilypond-git/build/out/bin:: > Relocation: compile datadir=, new > datadir=/tmp/build-lilypond-autobuild/out/share/lilypond//current > Relocation: framework_prefix=/tmp/build-lilypond-autobuild/out/bin/.. > Setting INSTALLER_PREFIX to /tmp/build-lilypond-autobuild/out/bin/.. > PATH=/tmp/build-lilypond-autobuild/out/bin/../bin (prepend) Setting > PATH > to > /tmp/build-lilypond-autobuild/out/bin/../bin:/tmp/build-lilypond-autobuild/out/bin:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/james/.local/bin:/home/james/bin:/home/james/lilypond-git/build/out/bin:: > Setting GUILE_MIN_YIELD_1 to 65 Setting GUILE_MIN_YIELD_2 to 65 Setting > GUILE_MIN_YIELD_MALLOC to 65 Setting GUILE_INIT_SEGMENT_SIZE_1 to > 10485760 Setting GUILE_MAX_SEGMENT_SIZE to 104857600 > > LILYPOND_DATADIR="/usr/local/share/lilypond/2.19.58" > LOCALEDIR="/usr/local/share/locale" > > Effective prefix: > "/tmp/build-lilypond-autobuild/out/share/lilypond/current" > PATH="/tmp/build-lilypond-autobuild/out/bin/../bin:/tmp/build-lilypond-autobuild/out/bin:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/tmp/build-lilypond-autobuild/lily/out:/tmp/build-lilypond-autobuild/scripts/build/out:/tmp/build-lilypond-autobuild/scripts/out:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/james/.local/bin:/home/james/bin:/home/james/lilypond-git/build/out/bin::" > [] > Guile 1.8 > [/tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily-library.scm/tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily.scmBacktrace: > In /tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily.scm: > 658: 0* [for-each #<procedure ly:load #> #] > In unknown file: > ?: 1* [ly:load "lily-library.scm"] > In /tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily.scm: > 507: 2* (let* ((file-name (%search-load-path x))) (ly:debug "[~A" > file-name) ...) 511: 3* [primitive-load-path > "/tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily-library.scm"] > > /tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily.scm:511:5: > In procedure scm_i_lreadparen in expression (primitive-load-path > file-name): > /tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily.scm:511:5: > /tmp/build-lilypond-autobuild/out/share/lilypond/current/scm/lily-library.scm:1051:1: > end of file > > > > --snip-- > > Obviously this went through a normal countdown and unless I made a > mistake with my patch testing (remember it is all still manually done) > then I don't know why it was not picked up at the time. > > Could someone else verify this on their own machines? > > Else check git master and if staging is still not merged and the time > difference is more than 2 hrs old (the cycle that my server at work > merges staging) then it isn't just me after all. > > > James
Hi James, accidently I permanently deleted the branch where the patch for issue 5099 was. But I had it as git-formated patch, so I reapplied it to a new branch and pushed from there. I've now retested make successfully, though. So I've no clue what's wrong. Cheers, Harm _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
