Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-05 Thread Mike Frysinger
On 05 Feb 2018 11:10, Mike Frysinger wrote: > On 05 Feb 2018 10:30, Philipp Thomas wrote: > > * Russ Allbery (ea...@eyrie.org) [20180203 02:57]: > > > > > I believe directory names including colons are simply not supported for > > > LD_LIBRARY_PATH (and various other things, such as PATH). > > >

Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-05 Thread Mike Frysinger
On 05 Feb 2018 10:30, Philipp Thomas wrote: > * Russ Allbery (ea...@eyrie.org) [20180203 02:57]: > > > I believe directory names including colons are simply not supported for > > LD_LIBRARY_PATH (and various other things, such as PATH). > > No no no, you get me wrong! What I meant is that colons

Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-05 Thread Philipp Thomas
* Bob Friesenhahn (bfrie...@simple.dallas.tx.us) [20180202 21:01]: > Are you saying that your system includes colons in its filesystem paths? > That would definitely be problematic. Not the system but the open build service uses colons in path names, but you also have to use colons for passing re

Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-05 Thread Philipp Thomas
* Russ Allbery (ea...@eyrie.org) [20180203 02:57]: > I believe directory names including colons are simply not supported for > LD_LIBRARY_PATH (and various other things, such as PATH). No no no, you get me wrong! What I meant is that colons *are* separators for entries in LD_LIBRARY_PATH and PATH

Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-02 Thread Russ Allbery
Philipp Thomas writes: > The wrapper script created by ltmain 2.4.6 on Linux sets LD_LIBRARY_PATH > as an absolute path. Unfortunately it doesn't escape colons and the > colon is the delimiter for paths in LD_LIBRARY_PATH. So the exe doesn't > find its library. > Could someone help me locate the

Re: Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-02 Thread Bob Friesenhahn
On Fri, 2 Feb 2018, Philipp Thomas wrote: The wrapper script created by ltmain 2.4.6 on Linux sets LD_LIBRARY_PATH as an absolute path. Unfortunately it doesn't escape colons and the colon is the delimiter for paths in LD_LIBRARY_PATH. So the exe doesn't find its library. Could someone help me

Colons not escaped for setting LD_LIBRARY_PATH.

2018-02-02 Thread Philipp Thomas
The wrapper script created by ltmain 2.4.6 on Linux sets LD_LIBRARY_PATH as an absolute path. Unfortunately it doesn't escape colons and the colon is the delimiter for paths in LD_LIBRARY_PATH. So the exe doesn't find its library. Could someone help me locate the place where I could modify the es