Re: autoreconf -i question

[John Calcote]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Wildenhues wrote:
> Hello,
> 
> * John Calcote wrote on Mon, Jun 09, 2008 at 05:32:23PM CEST:
>> Richard Ash wrote:
>>>> $ autoreconf -i
>>>> libtoolize: You should add the contents of the following files to
>>>> `aclocal.m4':
>>>> libtoolize:   `/usr/local/share/aclocal/libtool.m4'
> [...]
>>>> 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?
> 
> Do something like:
> - create a directory m4
> - add a line 'ACLOCAL_AMFLAGS = -I m4' to Makefile.am
> - add 'AC_CONFIG_MACRO_DIR([m4])' to configure.ac
> - run 'libtoolize --install'
> 

Thanks Ralf. This worked great. Now when I run autoreconf -i, I get the
following output:

libtoolize: putting auxiliary files in `.'.
libtoolize: `./ltmain.sh' is already up to date.
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'
libtoolize: putting auxiliary files in `.'.
libtoolize: `./ltmain.sh' is already up to date.
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: `m4/libtool.m4' is already up to date.
libtoolize: `m4/ltoptions.m4' is already up to date.
libtoolize: `m4/ltsugar.m4' is already up to date.
libtoolize: `m4/ltversion.m4' is already up to date.
libtoolize: `m4/lt~obsolete.m4' is already up to date.

It's a bit chattier (as you mentioned) than it probably should be, but
it works just fine. When I use just autoreconf, then all is well and quiet.

I see now what you're talking about wrt libtoolize steering you toward a
specific policy. Libtoolize appears to want you to use the "m4
directory" method, rather than the "copy everything into aclocal.m4"
method. Actually, I don't mind this, now that I know about it. Perhaps a
paragraph in the doc about it would help others...

Regards,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFITWBYdcgqmRY/OH8RAv3lAJ9Ylpo3Xt8yIWcquv8IA9kS/ufmggCfY48w
xCmH5/3+WqsMugG+rNT4tkQ=
=7vzs
-----END PGP SIGNATURE-----