Graham Percival <[email protected]> writes: > On Thu, Dec 22, 2011 at 10:39:20PM +0100, David Kastrup wrote: >> David Kastrup <[email protected]> writes: >> >> > Well, I've not been able to nicely redo the merges (git !@#$!#). So I >> > just threw everything release-related out of staging. If you redo the >> > merge into staging and the version number bump in staging, you should be >> > fine. >> >> I'm off to bed right now. Hope that Patchy will find things to its >> liking again. > > Apparently not; I started a rebuild ages ago. I've never quite > seen this, though -- rather than failing a build, make doc simply > appears to have hung! > > make -C ../../Documentation/po out=www messages > find ./out-www \( -name '*.??.idx' \) | sed 's!./out-www/!!g' | > xargs > /main/large-tmp/lilypond-autobuild/build/scripts/build/out/mass-link > hard ./out-www > /main/large-tmp/lilypond-autobuild/build/Documentation/./out-www > touch out-www/translation-lily-images > ls: cannot access ../../Documentation/snippets/*.ly: No such file > or directory > make[4]: Entering directory > `/main/large-tmp/lilypond-autobuild/build/Documentation/po' > /main/large-tmp/lilypond-autobuild/./Documentation/po/GNUmakefile:28: > warning: overriding commands for target `po-update' > /main/large-tmp/lilypond-autobuild/stepmake/stepmake/podir-targets.make:14: > warning: ignoring old commands for target `po-update' > make[4]: Nothing to be done for `messages'. > make[4]: Leaving directory > `/main/large-tmp/lilypond-autobuild/build/Documentation/po' > touch out-www/doc-po > > > Anybody have ideas? At first glance it seems like somebody used a > relative directory instead of doing it with $(top-src-dir).
No idea. But the symptom would suggest that commit 77cfd9e80a9792737a8630ba3c3ecfb359950f9d Author: Francisco Vila <[email protected]> Date: Wed Dec 21 22:54:53 2011 +0100 Web: remove web/ in some pathnames. could be a likely candidate for backing out and retesting. The other recent changes seem less probable. git grep /web/ still puts out a number of occurences, so maybe it was not complete? A total hang can be some command that expects to see file names on its command line, and getting to see none, instead of reading the named files tries reading standard input. And thus is waiting for your input on the tty. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
