Re: Libraries without SONAME

On Tue May 14, 2019 at 04:38:48PM +0100, Stuart Henderson wrote:
> On 2019/05/13 20:38, Antoine Jacoutot wrote:
> > On Mon, May 13, 2019 at 08:20:22PM +0200, Christian Weisgerber wrote:
> > > All shared libraries should have a SONAME:
> > >
> > > $ readelf -d /usr/lib/libc.so.95.0 | fgrep '(SONAME)'
> > > 0x000000000000000e (SONAME) Library soname: [libc.so.95.0]
> > >
> > > I ran a throwaway script over the packages from an amd64 bulk build,
> > > and the libraries listed below lack a SONAME. We fixed libtool to
> > > add the SONAME, so these must have been built differently. It makes
> > > little sense to approach this port by port; instead we should look
> > > for commonly used build tools that fail to embed SONAME and fix
> > > those. Sui generis cases can be cleaned up later.
> >
> > Thanks for the list naddy.
> > First quick win would be to fix cmake...
>
> Definitely - it is already producing confusing results for multipackage
> ports including libraries.
>

I'll give it a try.

RS