also sprach Michael K. Edwards <email@example.com> [2004.12.07.2147 +0100]: > So the server core can load these shared libraries with dlopen(), get > the "factory" routines with dlsym(), With dlopen(), why care about rpath or LD_LIBRARY_PATH? Just give the full path or implement your own search path. > In a perfect world, I'd give the libraries reasonably unique names > and proper SONAMEs, drop them in /usr/lib, and not need RPATH. > But what are the disadvantages to an absolute RPATH (not that > ../lib kludge) as long as there are other reasons why the > installed path to the binary has to be determined at build time? I'll leave this up to be answered by some folks who witnessed the libc6 migration from the first row. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <firstname.lastname@example.org> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
Description: Digital signature