Re: CVS libtoolize wants to read unexisting aclocal.m4

>>> "Gary" == Gary V Vaughan <gary@xxxxxxx> writes:

 Gary> On 13 Apr 2004, at 22:07, Alexandre Duret-Lutz wrote:
 >> Ahem... libtoolize should be called before aclocal, and yet it
 >> tries to reads the file produced by aclocal...

 Gary> It can't run autoconf --trace, and needs to see whether libltdl is
 Gary> used, where the macro directory is etc.  I think it is okay to look
 Gary> in aclocal.m4 if it is there, I just hadn't discarded the error
 Gary> message properly until libtool--devo--1.0--patch-44.

It's probably useful only when aclocal is not used (i.e.,
aclocal.m4 is handmade).  Otherwise aclocal.m4 will be a
collection of m4_include from which you won't learn anything.


I feel it might be worth moving away from the traditional

       fooize  # install foo's macros and aux files
       aclocal
       autoconf

to something like

       aclocal --copy # copy system-wide macros locally
       autoconf
       fooize         # install only foo's aux files

That way `fooize'-like tools can trace all they want in configure.ac.

(Actually the `--copy' thing does not exist yet, but whether the
macro is inserted in aclocal.m4 or installed in the tree and
m4_included makes no difference for this scheme.)
-- 
Alexandre Duret-Lutz