[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.1
From: |
lilypond |
Subject: |
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile |
Date: |
Fri, 27 May 2011 11:47:43 +0000 |
Comment #24 on issue 1562 by jan.nieuwenhuizen: using \sans on Windows
gives 'gs' error (2.13.53) fails to compile
http://code.google.com/p/lilypond/issues/detail?id=1562
Thanks. It's still there, trying to read:
C:\ProgramData\Symantec\Definitions\VirusDefs\TMP37CC.TMP
Any idea how gs gets pointed to that location?
I asked you to use a new full ghostscript-9.02 package but see that
I failed to provide the link.
Here's a link to a full, fresh ghostscript 9.02 package
to be unpacked at the same spot (it includes usr/).
http://lilypond.org/~janneke/ghostscript-9.02.zip
And yes, if this does not work, then a procmon log with an
identical run that succeeds on no-SP1 could be helpful.
Thanks!
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, (continued)
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/24
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/24
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/24
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/25
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/26
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/26
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/26
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/26
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/27
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/27
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile,
lilypond <=
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/28
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/29
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/30
- Message not available
- Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 2011/05/30