libtool and it's use of -rpath
I'm seeing an increasing number of upstream sources using libtool.
This is generally good since it makes generation of shared libraries
much easiser. There is a serious problem with libtool, however. It
insists on using -rpath.
For those that don't know, -rpath hardcodes the full path to the
library into the library itself and any binaries which use it. This
is done do the dynamlic linker can find the libraries. In Linux, we
have a much more flexible mechanism for doing this in /etc/ld.so.conf.
Using -rpath makes it impossible for us to move libraries around
(e.g. moving libc5 libraries to /usr/lib/libc5-compat) or use drop-in
replacements such as Xaw3d.
I suggest we modify libtool for Debian to not use -rpath. Comments?
David
--
David Engel ODS Networks
david@sw.ods.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . Trouble?
e-mail to templin@bucknell.edu .
Reply to: