[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: shrext and Autoconf

From: Peter O'Gorman
Subject: Re: shrext and Autoconf
Date: Thu, 30 Sep 2004 12:14:43 +0900
User-agent: Mozilla Thunderbird 0.7.3 (Macintosh/20040803)

Fabrice Bauzac wrote:

Hello there,

First, thanks to everyone.  Maintaining libtool is far from being an
easy task, while it is such a useful tool.

I think I have discovered a problem in current versions of libtool
(1.5.6 to 1.5.10 at least).

I use libtool with Autoconf.  When "configure" is run, a file
"libtool" is generated.  Let's call that file "GEN" instead of its
real name to avoid confusion.  That file is created from different
sources, notably configure itself and ltmain.sh.

configure inserts several lines into GEN.  Among them:

# Shared library suffix (normally ".so").

ltmain.sh inserts several lines into GEN.  Among them:

# Darwin sucks
eval std_shrext=\"$shrext_cmds\"

The same ltmain.sh variable is now called shrext_cmds, but was called
shrext before in GEN.  It means that there are problems with library
extensions if we use Autoconf 2.59 with current versions of libtool.

I'm the maintainer of a library, libcdaudio.  The shrext issue does
not prevent my library from installing and functionning correctly on
my Debian GNU/x86 system, but the library is installed as
libcdaudio.1.0.0 instead of libcdaudio.so.1.0.0.

I guess it has an impact on portability.

Just to let you know.

If you need to contact me, please CC: to my e-mail address, since I'm
not a subscriber of bug-libtool.


This issue is due to a mismatch in your libtool.m4 and ltmain.sh. I guess you have set up your PATH somewhat like mine "/usr/local/bin:/bin:/usr/bin" (well, I cut some stuff out). Assuming the first libtoolize in your path is /usr/local/bin/libtoolize and the first aclocal in your path is /usr/bin/aclocal then you will get an ltmain.sh from /usr/local/share/libtool/ and you'll get the m4 stuff for configure from /usr/share/aclocal/libtool.m4.

There are a couple of ways of dealing with this, the one I use is to always have all the autotools installed in each prefix where I want any of them. So I have /usr/local/bin/aclocal and /usr/local/bin/autoconf etc...

If the correct libtool.m4 is used then you will not see this problem. I think Gary fixed HEAD so that it checks that libtool was generated from the same versions of libtool.m4 and ltmain.sh.

Peter O'Gorman - http://www.pogma.com

reply via email to

[Prev in Thread] Current Thread [Next in Thread]