Subject: Re: Shared library symlinks and libtool
To: None <firstname.lastname@example.org>
From: Nick Hudson <email@example.com>
Date: 01/24/2001 15:07:49
> On Wed, 24 Jan 2001, Nick Hudson wrote:
> > firstname.lastname@example.org wrote:
> > >
> > > On Wed, 24 Jan 2001, Nick Hudson wrote:
> > [...]
> > > > are there any other examples?
> > >
> > > there are some other examples (non-libtool I think) of pkgs which don't
> > > automatically install ELF symlinks. security/openssl and security/PAM
> > > come to mind.
> > These are easy to deal with wrt PLIST though - right?
> yes, but I was unsure if the correct fix was to change the PLIST or to
> make the package install the symlinks. Especially in openssl where the
> install targetis in the package Makefile
Er, probably make the package install the symlinks. Although the easiest way to deal with a.out/ELF differences and to get the right
links is to use bsd.lib.mk or libtool.
aka email@example.com, firstname.lastname@example.org