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
* 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
* 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
I'm maintaining libtool for SuSE/Novell and have a problem where I would
need help from upstreams. You just released 2.2.6a to fix the local load
problem. The CVE says that libtool 1.x is also affected but sources have
changed enough so that the fix for 2.x can't be applied. In particular the
li
* Bob Friesenhahn (bfrie...@simple.dallas.tx.us) [20091124 18:34]:
> >I'm maintaining libtool for SuSE/Novell and have a problem where I would
> >need help from upstreams. You just released 2.2.6a to fix the local load
> >problem.
>
> You need 2.2.6b (not 'a'!) to fix the problem.
Sorry, I did
