|
From: | N. Andrew Walsh |
Subject: | Re: LD_LIBRARY_PATH in different installation contexts |
Date: | Tue, 11 Apr 2017 17:47:25 +0200 |
b) Linux, self-compiled
I've never experienced this issue with self-compiled LilyPonds. I assume this is *not* because self-compiled versions implicitly use the bundled libs but because they implicitly compile against what is available in the system. But if that assumption is correct I'd experience the same issue if I should run a self-compiled Lilypond that has been compiled some time ago, e.g. before a major Linux upgrade.
[Prev in Thread] | Current Thread | [Next in Thread] |