[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error with -dseparate-log-files

From: Phil Holmes
Subject: Re: error with -dseparate-log-files
Date: Tue, 21 Aug 2012 09:48:09 +0100

----- Original Message ----- From: "Colin Hall" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, August 21, 2012 9:24 AM
Subject: Re: error with -dseparate-log-files

On Mon, Aug 20, 2012 at 10:43:54AM +0100, Phil Holmes wrote:
"eluze" <address@hidden> wrote in message
>running the command
>lilypond -dseparate-log-files a.ly ab.ly
>results in:
>GNU LilyPond 2.15.95
>C:/Program Files
>(x86)/LilyPond/usr/share/lilypond/current/scm/lily.scm:807:15: In
>open-file in expression (open-file (if # # ...) "a"):
>C:/Program Files
>(x86)/LilyPond/usr/share/lilypond/current/scm/lily.scm:807:15: No
>such file
>or directory: "/dev/stderr"
>workaround (for windows):
>FOR %x IN (*.ly) DO lilypond %x [1>"%~nx.out"]  2>"%~nx.log"
>did I use this command/option incorrectly? if not I will add this to the
>issue list.

Definite bug for windows.  Don't believe dev/stderr should be used here:

             (open-file (if (string-or-symbol? (ly:get-option 'log-file))
(format #f "~a.log" (ly:get-option 'log-file))
                    "/dev/stderr") "a") #f))

David will know, but I suspect current-error-port or somesuch should
be used.

Looks like there are two bugs here:

1. Eluze reported that -dseparate-log-files does not work on Windows.

2. Lilypond running on Windows attempted to use /dev/stderr, which is not
available on the Windows platform.

I see that David has opened a tracker for the code attempting to use /dev/stderr.


I'll create a tracker for the -dseparate-log-files problem.



Colin Hall

I think it's the same bug. -dsepetc. doesn't work on windows because dev\stderr doesn't exist on Windows.

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]