GUB, using the release-2.14 branch, dies on linux-x86::lilypond-doc. Apparently our docs now contain something which uses a code path which we never used before?
This discussion: http://stackoverflow.com/questions/5090881/libgcc-s-so-undefined-reference-to-stack-chk-failglibc-2-4 suggests to add -lc to the linker flags. Does that sound like a good idea? or might this just be some crazy one-off error? The darwin-ppc build failed on one of our .o files, but when I tried recompiling it, GUB didn't complain again until the lilypond-doc stage. make[4]: Leaving directory `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/input/regression/musicxml' make[4]: Entering directory `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/input/regression/abc2ly' true make[4]: Leaving directory `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/input/regression/abc2ly' /main/src/gub/target/tools/root/usr/lib/libltdl.so.7: undefined reference to `__stack_chk_fail@GLIBC_2.4' collect2: ld returned 1 exit status make[1]: *** [out/lilypond] Error 1 make[1]: Leaving directory `/main/src/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily' _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
