On Jan 30, 1999, Marcus Brinkmann <[EMAIL PROTECTED]> wrote: > So you would have /usr/lib/libfoo.2 as rpath, but > really would use /usr/lib/libfoo-libc6.2 or libfoo-libc5.2, you get the > idea.
Just a minor nit: rpaths and sonames are independent of one-another. Although it is possible to arrange that sonames contain full pathnames, that's not what happens if you link a program with --rpath /usr/lib -lfoo. The --rpath switch will just add /usr/lib to a hard-coded search path, and -lfoo will just add the soname of libfoo to the list of run-time dependencies of a program. It is possible, though, to create a shared library with `-soname /usr/lib/libfoo.so.2', but then it becomes absolutely impossible to move the library around. There are times when this behavior is desirable, but libtool never does this, and there is no way to tell libtool to do it. -- Alexandre Oliva http://www.dcc.unicamp.br/~oliva [EMAIL PROTECTED] [EMAIL PROTECTED],gnu.org,egcs.cygnus.com,samba.org} Universidade Estadual de Campinas, SP, Brasil
