On Wed, Aug 03, 2011 at 07:38:07PM +0200, David Kastrup wrote: > > /Documentation/snippets" -I "/usr/local/tmp/lilypond/input/regression" -I > "/usr/local/tmp/lilypond/Documentation/included" -I > "/usr/local/tmp/lilypond/mf/out" -I "/usr/local/tmp/lilypond/mf/out" -I > "/usr/local/tmp/lilypond/Documentation/pictures" -I > "/usr/local/tmp/lilypond/Documentation/pictures/out-test" --formats=eps > -deps-box-padding=3.000000 -dread-file-list -dno-strip-output-dir > "/usr/local/tmp/lilypond/out/lybook-testdb/snippet-names--1980013010.ly" > Child returned 139 > > This is a rather recent development. Any ideas?
Take a look at the file names in /usr/local/tmp/lilypond/out/lybook-testdb/snippet-names--1980013010.ly and try them one-by-one until you find the failing file? when you find the filename, it'll be something like .../a7/lilypond-12deg87.ly inside that .ly file will be something like \sourcefile "Documentation/snippets/i-am-a-naughty-file.ly" you now finally have a filename that you can investigate on the command-line. ... hey, I never promised it'd be a *good* idea. But honestly, until we get some sensible logging for the build system (which could automatically identify the failing file!), you're SOL. 2 more days until GOP-PROP 5 is finalized and Phil can start working on this. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
