Updates:
Labels: -Patch-review Patch-needs_work
Comment #2 on issue 2759 by [email protected]: Patch: Don't use /dev/stderr which
is only defined on some systems
http://code.google.com/p/lilypond/issues/detail?id=2759
Too bad. With this patch, non-file specific error output gets diverted to
file-specific logs. See the comparison between the 2.15.96 behavior and
with this patch:
dak@lola:/tmp$ lilypond -dseparate-log-files a.ly b.ly
GNU LilyPond 2.15.96
Processing ./a
Processing ./b
Failed files: (b.ly a.ly)
dak@lola:/tmp$ cat a.log
warning: cannot find file: `a.ly'
dak@lola:/tmp$ cat b.log
warning: cannot find file: `b.ly'
fatal error: failed files: "b.ly a.ly"
dak@lola:/tmp$ /usr/local/tmp/lilypond/out/bin/lilypond
-dseparate-log-files a.ly b.ly
GNU LilyPond 2.17.0
dak@lola:/tmp$ cat a.log
Processing ./a
warning: cannot find file: `a.ly'
dak@lola:/tmp$ cat b.log
Processing ./b
warning: cannot find file: `b.ly'
Failed files: (b.ly a.ly)
fatal error: failed files: "b.ly a.ly"
dak@lola:/tmp$
Note, however, that even the old version puts _one_ message about both a.ly
and b.ly failing into b.log. Arguably equally wrong for split log files.
No idea how to go forward on this one. Maybe it needs ripping out
ly:redirect-stderr in some manner.
