On Sun, Jun 26, 2011 at 12:32:52AM +0200, Reinhold Kainhofer wrote: > Am Sonntag, 26. Juni 2011, 00:14:59 schrieben Sie: > > Yes, that was introduced in > > 3623cfc12bb53499a591ae45ac61931bafc6bf20 > > > > We've had some discussions about how to fix it, and we have a > > solid plan, but we didn't get as far as making a patch. > > > There's a corresponding .log file now (in the same directory); the > > error is there. > > Nope, that file is empty: > reinhold@einstein:~/lilypond/lilypond$ ls -la out/lybook-testdb/snippet- > names-1241278582.*log > -rw-rw-r-- 1 reinhold reinhold 0 2011-06-26 00:18 out/lybook-testdb/snippet- > names-1241278582.err.log > -rw-rw-r-- 1 reinhold reinhold 112 2011-06-26 00:18 out/lybook-testdb/snippet- > names-1241278582.log > > And the *err.log file only contains two snippet filenames, but no error.
Hmm. Since even I can't state with certainty what the next step would be to find the information about the failing build, this is clearly a huge problem. (I have several suspicions on where to look, but no certainty) I have reverted that commit; the build should behave as usual now. I'll take another look at this tomorrow, and we'll go through another "patch countdown" for whatever new patch we have. Sorry, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
