Re: libtool sonames and Compiled some packages

[Mark Kettenis <kettenis@wins.uva.nl>]

   Date: Tue, 1 Jun 1999 16:07:11 +0200
   From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>

   On Mon, May 31, 1999 at 11:21:16PM +0300, Kalle Olavi Niemitalo wrote:
   > aalib_1.2-14
   > ============
   > 
   > The code compiles and works fine, but the Debian scripts fail because
   > of unexpected shared library names.

   > That helped a bit, but now it couldn't find usr/lib/libaa.so.1.
   > There was usr/lib/libaa.so but debian/aalib1.files didn't want that.
   > 
   > In ltconfig, library_names_spec is still different between linux-gnu*
   > and gnu*.  Is this intentional?

   Ah, there is the code that cares about sonames :)

   In libtool 1.3.2 (you should defininitely use the unstable versions to
   compile packages), we have:

   For Linux:
   library_names_spec='${libname}${release}.so$versuffix ${libname}${release}.so$major $libname.so'

   For GNU:
   library_names_spec='${libname}${release}.so$versuffix $libname.so'

   I think we should have the same entries for gnu and linux (read: add the
   missing entry to the GNU field.

   Do the Hurd folks agree? Roland? Thomas? Mark? Gordon? Anyone? :)
   If yes, I will file a bug report.

Yep, but there's more.  I've already looked into it and promised the
upstream maintainer a patch by the end of this week.  I'll CC:
debian-hurd on that.  (Sorry, the patch is sitting at home while I am
at work right now).

Mark