Re: Ghostscript problem in 2.19.18

[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?

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

Is it executable?


gs requires its resource files (gs_init.ps etc.).
It finds them by environment variable GS_LIB or its built in search path.

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.
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.