Subject: Re: Shared library symlinks and libtool
To: Thomas Klausner <wiz@danbala.ifoer.tuwien.ac.at>
From: Todd Vierling <tv@wasabisystems.com>
List: tech-pkg
Date: 01/24/2001 10:33:47
On Wed, 24 Jan 2001, Thomas Klausner wrote:
: After Alistair's recent change to make ELF PLISTs default, some
: programs have problems in the installation phase. In particular, I
: think of devel/xdelta (and some others) where the problem lies in the
: fact that they install a library 'libfoo.so.1.2.3', and libtool only
: generates symlinks for 'libfoo.so.1' and 'libfoo.so'.
:
: What is the proper target to fix -- the PLISTs (removing the
: 'libfoo.so.1.2' entries)
Remove the entries if a teeny version is used. There are exactly *three*
parts to an ELF shlib:
libfoo.so.major.minor[.teeny] -> actual file (not used directly)
libfoo.so.major -> symlink used at runtime (thanks to -soname)
libfoo.so -> symlink used at link-time (during program compiles)
If a teeny version is used, there should *not* be a libfoo.so.major.minor
symlink; that file will never get used.
--
-- Todd Vierling <tv@wasabisystems.com> * Wasabi NetBSD: Run with it.
-- NetBSD 1.5 now available on CD-ROM -- http://www.wasabisystems.com/