<lilypond.patchy.jl...@gmail.com> wrote in
message news:4f81c580.c507b40a.6878.7...@mx.google.com...
Begin LilyPond compile, commit: eebdf598862812edf142f1c52a727c962bf26465
Merged staging, now at: e045a8a796ea14ac04838af850e89da3a9343bb0
Success: ./autogen.sh --noconfigure
Success: ../configure --disable-optimising
Success: nice make clean -j6 CPU_COUNT=6
*** FAILED BUILD ***
nice make -j6 CPU_COUNT=6
Previous good commit: 18cc52e04834f7eaec4d41cf2783767b0e764d03
Current broken commit: e045a8a796ea14ac04838af850e89da3a9343bb0
Begin LilyPond compile, commit: 1b473723a8acf07a58f44561068fed212e5bcd98
Merged staging, now at: e045a8a796ea14ac04838af850e89da3a9343bb0
Success: ./autogen.sh --noconfigure
Success: ../configure --disable-optimising
Success: nice make clean -j6 CPU_COUNT=6
*** FAILED BUILD ***
nice make -j6 CPU_COUNT=6
Previous good commit:
Current broken commit: e045a8a796ea14ac04838af850e89da3a9343bb0
This is my LSR update. It was OK on my machine, but I'll run patchy myself
and see what's going on.
--
Phil Holmes
Bug Squad
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
