|
From: | Urs Liska |
Subject: | Re: GhostScript Fail (regression 2.19.17 to 2.19.18) |
Date: | Tue, 23 Jan 2018 10:17:01 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 |
Hi Andrew(s) Am 22.01.2018 um 23:07 schrieb Andrew
Smith:
No guarantee it works for you, but I have a strong suspicion. When installing LilyPond the normal way from the downloaded archive it creates a wrapper command "lilypond" (usually as ~/bin/lilypond). This doesn't only call the lilypond executable but also adds export LD_LIBRARY_PATH=/path/to/lilypond/usr/lib:$LD_LIBRARY_PATH to make sure the libraries shipped with LilyPond are used and avoid such version mismatches with system libraries. I'm not sure how lyp invokes LilyPond but you should look into this (and maybe call LilyPond directly/through a custom wrapper script). We had to learn that with Frescobaldi too. Frescobaldi can manage arbitrary LilyPond installations, and by now it injects that library path (for the chosen LilyPond) in the invocation command. HTH Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |