Re: Updating libtool in GCC and srctree

[Alexandre Oliva <aoliva at redhat dot com>]

On Mar  9, 2007, Steve Ellcey <sje@cup.hp.com> wrote:

> If I just run autoconf I get errors because I am not
> including the new ltoptions.m4, ltsugar.m4, and ltversion.m4 files.

I'd just prepend them to our local copy of libtool.m4, pretty much
like aclocal would have done into aclocal.m4.

> But boehm-gc has no acinclude.m4 file

That's equivalent to an empty one.  I'd guess an existing acinclude.m4
was removed in a merge or something like that, because its aclocal.m4
couldn't possibly contain the sinclude statements it does otherwise.
Unless someone added them to an aclocal-generated file, which doesn't
seem to match this file's history.

How about copying the m4_include statements to acinclude.m4,
(incorrectly) removed a while ago, and then re-create aclocal.m4 with
aclocal?

> and while libffi has an acinclude.m4 file, it doesn't have an
> include of libtool.m4.

This is a bug similar to that of boehm-gc above.

> So my question is, how is the include of libtool.m4 getting into
> aclocal.m4?

Magic ;-)

Someone probably failed to realize that they should be in acinclude.m4
in order for them to survive an aclocal run.

> This is aclocal 1.9.6.  Any idea on what I need to do here to fix this
> error?  Why do some acinclude.m4 files have explicit includes for
> libtool files (libgfortran, libgomp, etc) but other's don't (libffi,
> gcc).

libffi/ is a bug (it's in aclocal.m4, but not in acinclude.m4).  gcc/
doesn't use libtool at all.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}