Re: Shared library defines a RPATH
Will Newton <email@example.com> immo vero scripsit:
> > plugins don't need rpath.
> > You can just point to its full path in dlopen.
> Sorry, bad example. What I meant was - I have a package with lots of
> libraries that have have non-descriptive names like e.g. libdd.so that are
> likely to cause namespace collisions, so I have placed them in a subdir of
> /usr/lib. AFAIK at the present time this program is the only one to use these
> shared libs. Is it correct for this program to have rpath set to this
I have no idea why they should be a shared library at all
in the first place.
firstname.lastname@example.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org