Re: Colons not escaped for setting LD_LIBRARY_PATH.

Mike Frysinger <[email protected]> Mon, 5 Feb 2018 16:49:00 -0500

Newsgroups	gmane.comp.gnu.libtool.general
Message-ID	<20180205214900.GG27582@vapier>

On 05 Feb 2018 11:10, Mike Frysinger wrote:
> On 05 Feb 2018 10:30, Philipp Thomas wrote:
> > * Russ Allbery ([email protected]) [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. But now I guess it's more an issue with
> > bash then with libtool as libtool hasn't changed in quite a few years but
> > bash has. So at least for now it seems like a false alarm.
> 
> bash doesn't parse LD_LIBRARY_PATH, and way more than bash parses PATH
> 
> but Russ is correct: at least glibc does not have any mechanism for escaping
> colons in LD_LIBRARY_PATH.  it is simply not supported.
> https://sourceware.org/git/?p=glibc.git;a=blob;f=elf/dl-load.c;hb=glibc-2.27#l738

fwiw, i've sent patches to the man-pages project to make it clear that
escaping the colons will not work.
https://www.spinics.net/lists/linux-man/msg12576.html
-mike

_______________________________________________
https://lists.gnu.org/mailman/listinfo/libtool

signature.asc (application/pgp-signature, 833 B)