[Top][All Lists]

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

Re: Constantly changing libtool

From: Laurence Marks
Subject: Re: Constantly changing libtool
Date: Thu, 15 Apr 2021 08:33:43 -0500

Unfortunately things are not consistent, and in general have not been for
some time. It all depends upon which version has been installed which is
sometimes (often) beyond the control/competence of users. Even someone who
is moderately competent can have problems. For instance, on my laptop I
have both cygwin & Ubuntu; my cluster has Centos. Some of my students have
VM and/or Mac-Unix, and who knows what other users in Russia/Japan/etc have
-- I can't control that. I typically install autoXYZ on my systems in
/use/local, but that is not a reliable or general fix.

When moving between machines/OS to test (as gcc & now gfortran are moving
targets) I almost always have to reconfig. Libtool is part of the issue,
but there are also couplings to aclocal macros and sometimes other
components as well.

In the same way as autoXZY sets up Makefiles in an OS independent fashion,
there should be a way to autoupdate autoXYZ files for each system without
user intervention. (I don't mean automake itself or similar, I do mean only
the local files.) In an ideal world this would be a macro in

Professor Laurence Marks
"Research is to see what everybody else has seen, and to think what nobody
else has thought", Albert Szent-Györgyi

On Thu, Apr 15, 2021, 08:12 Bob Friesenhahn <>

> On Wed, 14 Apr 2021, Laurence Marks wrote:
> > It is not timestamp issues, it is version issues -- e.g. libtool 2.4.2
> > versus 2.4.6 (for instance, those are just invented numbers). In many
> cases
> > aclocal, libtool, and maybe a few others do not work if they
> were
> > created with a different autoXYZ version than is on the computer where
> they
> > are being installed. It seems to be "special" to libtool.
> There has not been a libtool release since 2014 and it is 2021
> already.
> The issues you are complaining about should not be existing for quite
> a long time already, and are easily corrected by installing consistent
> Autotools versions under the same installation prefix.  If you don't
> like the archaic versions your system provides, then simply uninstall
> (or not use) those packages and install using current Autotools
> release versions.
> It is intended that libtool components are installed into the software
> which uses them.  This assures consistent versions.  If the libtool
> components were not installed and distributed with the package, then
> there could be problems as you describe.
> Bob
> --
> Bob Friesenhahn
> GraphicsMagick Maintainer,
> Public Key,

reply via email to

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