[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PDF size
Re: PDF size
Thu, 06 Apr 2006 13:51:00 +0200
Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.2) Gecko/20040906
Thanks, that was it!
Still, since the lilypond installer already contains a patched gs, there
had to some other problem.
As it turned out, the method lilypond uses to locate its gs binary is not
fool-proof: in my case, the lilypond 2.8.1 installation picked up the old
gs 8.15 binary from the 220.127.116.11 installation.
This is probably due to the following definition in
(search-executable '("gs-nox" "gs-8.15" "gs")))
lilypond 2.8.1 does not have gs-nox, but lilypond 18.104.22.168 does.
The old installation path was still in my PATH, so even though lilypond
2.8.1 prepends its own path to the PATH, the gs search first finds the old
By the way, "gs-8.15" does not really make sense here when the gs version
bundled with lilypond is 8.50.
On the whole, since lilypond comes with so many required libraries and
executables which are very likely to be already installed on the user's
system in different versions, it is a bit dangerous to rely on the PATH or
other enviroment variables. It would be safer to refer to all required
binaries relative to the installation root.
Mats Bengtsson schrieb:
I should have hinted you to also search the archives of
bug-lilypond. For example, you will find:
which tells that the culprit is Ghostscript and how to
fix it (if you're prepared to recompile Ghostscript).