>> How do you install lilypond-2.19.18-1.linux-x86.sh?
>
> I execute the script as user to install it to ~/lilypond (with the
> wrappers in ~/bin).
> Then (and that's maybe where the problem starts) I move the ~/lilypond
> folder to the location on /shared and create a symlink at ~/lilypond.
> Thi
Am 14.04.2015 um 16:22 schrieb Masamichi HOSODA:
OK.
Compiling a file with lilypond-2.19.18-1.linux-x86.sh ends with
Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
-r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.
> OK.
>
> Compiling a file with lilypond-2.19.18-1.linux-x86.sh ends with
>
> Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28
> -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
> -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite
> -fdocument.ps'...
>
>
>
Am 13.04.2015 um 16:47 schrieb Masamichi HOSODA:
gs: Interpreter revision (905) does not match gs_init.ps revision
(915).
lilypond-2.19.18-1.linux-x86.sh includes gs-9.15.
However, lilypond seems to be invoking the external gs-9.05
instead of included gs-9.15.
My ubuntu 64 bit environment hav
> gs: Interpreter revision (905) does not match gs_init.ps revision
> (915).
lilypond-2.19.18-1.linux-x86.sh includes gs-9.15.
However, lilypond seems to be invoking the external gs-9.05
instead of included gs-9.15.
My ubuntu 64 bit environment have been installed gs-9.10.
However, lilypond invok
> I have just installed lilypond-2.19.18-1.linux-x86.sh on another
> machine running Debian 7 stable with latest updates. And the error is
> identical. Maybe (this is a big maybe) I'll have a chance to test it
> on another (different) 32bit Linux installation later today, but
> that's not sure at a
Am 13.04.2015 um 16:04 schrieb Masamichi HOSODA:
I have just installed lilypond-2.19.18-1.linux-x86.sh on another
machine running Debian 7 stable with latest updates. And the error is
identical. Maybe (this is a big maybe) I'll have a chance to test it
on another (different) 32bit Linux installat
Am 13.04.2015 um 14:19 schrieb Masamichi HOSODA:
This is on Debian with the linux-386 binary and applies to _any_ file,
even
{ c }
.
Compiling with the 2.19.17 binary works.
Compiling with the 2.19.18 binary fails.
Compiling with a custom build from current master works.
As there are no relevan
> This is on Debian with the linux-386 binary and applies to _any_ file,
> even
> { c }
> .
>
> Compiling with the 2.19.17 binary works.
> Compiling with the 2.19.18 binary fails.
> Compiling with a custom build from current master works.
>
> As there are no relevant commits between the 2.19.18 t
2015-04-13 10:21 GMT+02:00 Urs Liska :
> Hi,
>
> just trying out the binary releases again, and I notice that with 2.19.18
> all documents fail with the following message:
>
> Layout output to `document.ps'...
>
> Converting to `./document.pdf'...
>
> warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=5
Hi,
just trying out the binary releases again, and I notice that with
2.19.18 all documents fail with the following message:
Layout output to `document.ps'...
Converting to `./document.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLev
11 matches
Mail list logo
