Re: Ghostscript problem in 2.19.18

[Urs Liska]

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.setpdfwrite
> > -fdocument.ps'...
> >
> >
> > gs: Interpreter revision (905) does not match gs_init.ps revision
> > (915).
> >
> > warning: `(gs -dSAFER -dDEVICEWIDTHPOINTS=595.28
> > -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
> > -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite
> > -fdocument.ps)' failed (256)
> >
> >
> >
> > while compiling with a self-built version 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'...
> >
> > GPL Ghostscript 9.05 (2012-02-08)
> >
> > Copyright (C) 2010 Artifex Software, Inc. All rights reserved.
> >
> > This software comes with NO WARRANTY: see the file PUBLIC for details.
> >
> > ]/home/uliska/git/lilypond/lilypond-builds/current/out/share/lilypond/current/scm/lily.scm
> >
> >
> > Success: compilation successfully complete
> >
> >
> > Here we obviously call Ghostscript 9.05 also (which seems to be the
> > "current" version on Debian stable) but without conflicting with
> > "gs_init.ps".
> >
> >
> > So what is wrong here?
> > If it is simply an issue with my personal installation I'd consider
> > ignoring it, but somehow this looks like an issue. So it would be good
> > to have a confirmation that either I'm the only one experiencing it or
> > not.
> 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.
This is what I've always done and what has always worked.

> In your system, does
> /shared/software/lilypond/current-devel/usr/bin/gs
> exist?
>
> Is it executable?

Yes:
-rwxr-xr-x 1 uliska uliska    4936 Apr  5 16:13 gs
> gs requires its resource files (gs_init.ps etc.).
> It finds them by environment variable GS_LIB or its built in search path.

echo $GS_LIB doesn't return anything.
> lilypond-2.19.18-1.linux-x86.sh includes gs-9.15 executable
> and its resource files.
>
> I think that this issue is as following.
>
> In your environments, the case of lilypond-2.19.18-1.linux-x86.sh,
> lilypond invokes system's gs-9.10 instead of included gs-9.15.

If I run gs --version on the gs file inside the lilypond-2.19.18-1 
installation it returns "9.05"!

> But, GS_LIB indicates included resource files for gs-9.15.
> The versions of gs executable and gs resource files are different.
> Then, it fails.
>
> In the case of your self-built, lilypond invokes system's gs-9.10
> (self-built lilypond doesn't include gs executable),
> GS_LIB is maybe unset
> (self-built lilypond doesn't include gs resource files),
> and gs finds system's gs resource files for gs-9.10.
> The versions of gs executable and gs resource files are same gs-9.10.
> Then, it succeeds.
>
> In my environments, the case of lilypond-2.19.18-1.linux-x86.sh,
> lilypond invokes included gs-9.15,
> and GS_LIB indicates included resource files for gs-9.15.
> The versions of gs executable and gs resource files are same gs-9.15.
> Then, it succeeds.
>
> I think the problem of your system is
> why lilypond invokes system's gs instead of included gs.

I just installed 2.19.18-1 again and left it in its default location 
~/lilypond.
Now everything works.

Can it be that there's some hardcoded path anywhere, so the included gs 
isn't found anymore?
But if that's the case I think it should be fixed because I should be 
able to move around the actual lilypond installation - and it did work 
up to 2.19.17

Urs