Building it manually, I see this: cd ./out-www; texi2pdf -I /home/gperciva/src/lilypond/Documentation -I /home/gperciva/src/lilypond/input/regression --quiet collated-files.texi Error (196): Command token too long ^Cmake[3]: *** Deleting file `out-www/collated-files.pdf' /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
Does anybody feel like doing a git bisect on staging to find out what broke it? In theory, we could make a copy of the curent staging branch, do a few bisects, then set staging to be the last buildable version... just to get *some* of the recent commits into master, while others investigated the breakage. Unfortunately this doesn't seem to affect a normal "make" or "make test", otherwise Patchy should have found it at the Patch-review stage. So you're stuck doing a full doc build at each stage. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
