Re: autoreconf not passing -I option to aclocal

[Guillaume Rousse]

Eric Blake wrote:
> According to Guillaume Rousse on 9/28/2006 7:09 AM:
>>>>>> autoreconf-2.5x: running: aclocal
>>>> Sounds like you forgot to do
>>>> ACLOCAL_AMFLAGS = -I ../autoconf
>>>>
>>>> in your Makefile.am.
>>> I forgot to precise that I'm not using automake...
> 
> aclocal is part of automake.  autoreconf should not be running it if
> detects that you are not using automake.
I disagree: aclocal is useful even when you don't use automake, for
importing your own macros as in my case, so you should have a way to
force its invocation if needed. Unless autoconf is now able to perform
macros lookup in external directories itself, as its invocation with
--include seems to suggest.

Anyway, my tests show that is is called unconditionally.

>  On the other hand, your
> screenshot looks like you are running a wrapper autoreconf, rather than
> the stock one provided by autoconf; perhaps it is a wrapper bug that you
> should report to the maintainer of the wrapper script?
I also tested direct invocation, with ACLOCAL, AUTOCONF and AUTOHEADER
envvar set:
address@hidden camlimages]$ autoreconf-2.5x -v -I ../autoconf/
autoreconf-2.5x: Entering directory `.'
autoreconf-2.5x: configure.ac: not using Gettext
autoreconf-2.5x: running: /usr/bin/aclocal-1.9
autoreconf-2.5x: configure.ac: tracing
autoreconf-2.5x: configure.ac: not using Libtool
autoreconf-2.5x: running: /usr/bin/autoconf-2.5x --include=../autoconf/
autoreconf-2.5x: running: /usr/bin/autoheader-2.5x --include=../autoconf/
autoreconf-2.5x: configure.ac: not using Automake
autoreconf-2.5x: Leaving directory `.'

As a sidenote, if configure scripts does not exists already (first
invocation), I got an error message about  possibly undefined macro. If
configure already exists, I don't have it.
-- 
Guillaume Rousse
Projet Estime, INRIA
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex - France