[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Shared library defines a RPATH



Will Newton <will@misconception.org.uk> 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 
> directory?

I have no idea why they should be a shared library at all 
in the first place.


regards,
	junichi

-- 
dancer@debian.org : Junichi Uekawa   http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: