Re: Colons not escaped for setting LD_LIBRARY_PATH.

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
-mike

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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAlp4ghEACgkQQWM7n+g3
9YFahxAAhso5SniyUG2lcWnCtGKIBtnYQafh0U95VUuWMS+EqT4tHyTmEicrOTzq
rP8XADY3MNBiXqbYcO0YYUnEQ1lxJLYwAWCrflcU0tv6MNz/rfYt34Oyh7o+IfPW
x4CZ7Upxp3YtNA+oqEHa3vFnec/SQzpkfB798tRhvSpUwaUtLTmd02JPMejmRBl4
ymQp4K8o8NBXZaj7iWS77YchYLzhL5Syt+ysV8B5yTc1KeKL8ZsosZch0g22Z+7r
/9UrcBDzR5EBwsV1emzPcA1K9syIftZAl9QRaKg2FBufO6k3r7JeTFq5V/ONAZCa
Cd9Kv9O91GqPV5gLxk5Knsh0+phu0xiWCHxY3Tt2u/UPMdxf9HYsgJQY9JDqtQck
yaVbAm2BWVgcyDTrcDXh3NOMlMlaV4A/lONVr1signJDj5TWBkmBuKTZHMkI2zJI
rOT1lHbDLbnBNx37At08r3hsBbjgpiJehAOpr8UhY+NAfH+4hbiKqtsNdPsq/u+R
G9LwiSIfgIueKuYMa2mqA0lBdRffuSn5H4+KRiWNqDaGbVRacUClwZCpNfUcvGrQ
YlySyK6Mly4sQB1nkcbwikHXNLX57OD8CIP1LUCtG6Arb81NwnDLvL2cIKkaIuoF
HyOfl5RyqRPj1Smf08QJMn6EVIjihwoYjIYXdXqHCEwdkJ4UqoM=
=1Es/
-----END PGP SIGNATURE-----