>> Which LT_INIT option would enable the hidden symbol visibility support?
>
> There is no such thing in libtool as far as I am aware. Libtool is all
> about supporting a core set of features in a portable way.
I was really asking to implement LT_INIT(elf-hidden) in the spirit of
LT_INIT(win32-dl
On Fri, 2 Feb 2018, Alexei Podtelezhnikov wrote:
Dear all,
Which LT_INIT option would enable the hidden symbol visibility support?
There is no such thing in libtool as far as I am aware. Libtool is
all about supporting a core set of features in a portable way.
There is nothing to prevent
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).
> >
>
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
* 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
* 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
