[Top][All Lists]

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

Re: autoreconf -i question

From: John Calcote
Subject: Re: autoreconf -i question
Date: Mon, 09 Jun 2008 09:32:23 -0600
User-agent: Thunderbird (X11/20080226)

Hash: SHA1

Hi (adding the libtool mailing list),

Richard Ash wrote:
>> $ autoreconf -i
>> libtoolize: putting auxiliary files in `.'.
>> libtoolize: copying file `./'
>> libtoolize: You should add the contents of the following files to
>> `aclocal.m4':
>> libtoolize:   `/usr/local/share/aclocal/libtool.m4'
>> libtoolize:   `/usr/local/share/aclocal/ltoptions.m4'
>> libtoolize:   `/usr/local/share/aclocal/ltversion.m4'
>> libtoolize:   `/usr/local/share/aclocal/ltsugar.m4'
>> libtoolize:   `/usr/local/share/aclocal/lt~obsolete.m4'
>> installing `./compile'
>> installing `./config.guess'
>> installing `./config.sub'
>> installing `./install-sh'
>> installing `./missing'
>> src/ installing `./depcomp'
>> My question: Do I REALLY need to copy all of those .m4 files into my
>> aclocal.m4 file? If so, why doesn't libtoolize (or aclocal) do that for me?
> Did you have an aclocal.m4 file before you started? If so, I suspect
> that aclocal won't touch it in case it contains important stuff you
> don't want to loose.

No, that's the strange part - I apologize for not being more clear to
begin with. This project is a rather simple autoconf/automake/libtool
project, that has NO hand-coded aclocal.m4 OR acinclude.m4 files. The
output above was generated by running autoreconf -i. The -i flag (as you
 know) indicates to autoreconf that it should execute all of the
autotools (it thinks it needs to) with what ever options they require to
indicate that missing files should be installed.

I'm thinking that the reason for this output is that by the time
libtoolize is executed aclocal, autoconf and automake have already
generated an aclocal.m4 file. Then, when libtoolize get's around to
running, it appears to it as if someone has hand-written an aclocal.m4
file, which it then doesn't want to touch.

I wonder if libtoolize shouldn't support a "hidden" option that
autoreconf can pass, indicating that aclocal.m4 is generated by prior
tools, and it's okay to mess with it.

Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE -


reply via email to

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