Re: LD_LIBRARY_PATH in different installation contexts

Am 11.04.2017 um 18:18 schrieb Federico Bruni: > Il giorno mar 11 apr 2017 alle 18:09, Urs Liska > ha scritto: >> OTOH I may well fix this issue for Linux only, thinking that probably >> these error reports have only come from Linux users (?). > > I've never experienced this issue. > I've used D

Re: LD_LIBRARY_PATH in different installation contexts

2017-04-11 17:47 GMT+02:00 N. Andrew Walsh : > Hi Urs, List, > > On Tue, Apr 11, 2017 at 11:04 AM, Urs Liska wrote: >> >> 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 bundle

Re: LD_LIBRARY_PATH in different installation contexts

Il giorno mar 11 apr 2017 alle 18:09, Urs Liska ha scritto: OTOH I may well fix this issue for Linux only, thinking that probably these error reports have only come from Linux users (?). I've never experienced this issue. I've used Debian for several years and now Fedora since a couple of yea

Re: LD_LIBRARY_PATH in different installation contexts

Am 11.04.2017 um 17:55 schrieb Trevor Daniels: > Urs Liska wrote Tuesday, April 11, 2017 9:58 AM > >> e) Windows >> I can imagine this isn't an issue because everything has to be bundled >> anyway. >> But I don't know about that. Please help me by giving me that information. > Well, I've never

Re: LD_LIBRARY_PATH in different installation contexts

Am 11.04.2017 um 17:47 schrieb N. Andrew Walsh: > Hi Urs, List, > > On Tue, Apr 11, 2017 at 11:04 AM, Urs Liska > wrote: > > b) Linux, self-compiled > > I've never experienced this issue with self-compiled LilyPonds. I > assume this is *not* because self-

Re: LD_LIBRARY_PATH in different installation contexts

Urs Liska wrote Tuesday, April 11, 2017 9:58 AM > e) Windows > I can imagine this isn't an issue because everything has to be bundled > anyway. > But I don't know about that. Please help me by giving me that information. Well, I've never seen that problem running Frescobaldi under Windows Vis

Re: LD_LIBRARY_PATH in different installation contexts

Hi Urs, List, On Tue, Apr 11, 2017 at 11:04 AM, Urs Liska wrote: > 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

Re: LD_LIBRARY_PATH in different installation contexts

Hi David, thank you for the feedback. Am 11.04.2017 um 16:47 schrieb David Wright: > On Tue 11 Apr 2017 at 11:04:14 (+0200), Urs Liska wrote: >> I want to finally fix an issue in Frescobaldi that has bugged me for a >> long time, but I need some information on how LilyPond behaves in >> differen

Re: LD_LIBRARY_PATH in different installation contexts

On Tue 11 Apr 2017 at 11:04:14 (+0200), Urs Liska wrote: > I want to finally fix an issue in Frescobaldi that has bugged me for a > long time, but I need some information on how LilyPond behaves in > different installation types/contexts. > > For some time we had popping up reports about compilati

Re: LD_LIBRARY_PATH in different installation contexts

I don't know why the previous email was formatted so badly, I'll try it again Hi all, I want to finally fix an issue in Frescobaldi that has bugged me for a long time, but I need some information on how LilyPond behaves in different installation types/contexts. For some time we had popping up r

LD_LIBRARY_PATH in different installation contexts

Hi all, I want to finally fix an issue in Frescobaldi that has bugged me for a long time, but I need some information on how LilyPond behaves in different installation types/contexts. For some time we had popping up reports about compilation failures similar to this one warning: `(gs -q -dSAFER