Re: libtool generates temporary wrappers with improperly escaped LD_LIBRARY_PATH

[Brandon Philips]

On 07:37 Thu 18 Dec 2008, Ralf Wildenhues wrote:
> * Brandon Philips wrote on Thu, Dec 18, 2008 at 06:32:15AM CET:
> > 
> > I have found that libtool generates temporary wrappers with improperly
> > escaped LD_LIBRARY_PATH. If the current directory path contains a colon.
> > For example /home/philips/test:directory/attr-2.4.43/
> 
> Where is it documented that LD_LIBRARY_PATH is interpreted as with
> backslash escaping for colons in the names?  I've never heard of that
> before.
> 
> The ld.so(1) man page on my Debian testing system documents that
> LD_LIBRARY_PATH is interpreted similarly to PATH.  I confirmed now that
> PATH uses this kind of colon escaping, surprisingly.  I cannot find it
> documented anywhere though, certainly not in the Posix pages (but hey,
> I overlooked things before).
> 
> We can think about supporting it when and where this is suitably safe to
> do so, but my gut reaction would be "don't do it when it hurts".

I completely agree that people shouldn't do this. I wouldn't have
noticed usually but openSUSE uses colons as separators for project
names.

e.g.

osc co openSUSE:Factory attr

creates

./openSUSE:Factory/attr

BTW, I just tried it out and /home/philips/test\:directory/attr-2.4.43/
doesn't help. I guess this isn't a libtool bug until ld can accept some
type of escaping.

But, first, I will try to get openSUSE's build service to stop using
colons ;)

Cheers,

        Brandon