Re: ACLOCAL_AMFLAGS looks like no effect on make

[Oleg V. Zhylin]

> Just to be sure: you put the ACLOCAL_AMFLAGS line in the toplevel
> Makefile.am file?  The file is named exactly Makefile.am?  There is
> no whitespace before the word `ACLOCAL_AMFLAGS'?

Yes to all three. One further detail. As I debugged my package automake
eventually captured ACLOCAL_AMFLAGS value. But when I changed flags
again, the change was not reflected immediately.

--- Ralf Wildenhues <address@hidden> wrote:

> Hello Oleg,
> 
> * Oleg V. Zhylin wrote on Tue, Nov 27, 2007 at 12:52:52AM CET:
> > 
> >   This time I'm running Automake 1.10. According to "6.3.4 Handling
> > Local Macros" in the manual
> > 
> > ACLOCAL_AMFLAGS = -I m4
> > 
> >   line should instruct both autoreconf and make to use these flags
> when
> > autoconf is executed. But in my case autoreconf does use the flags
> > (autoreconf is nice enough to understand $ACLOCAL environment
> > variable), but as result of make the following line is print no
> matter
> > what
> > 
> > cd . && /bin/sh /home/ovz/Work/SalfordD_GNU_Build/missing --run
> > aclocal-1.10 
> > 
> > i.e. no -I parameter.
> 
> Just to be sure: you put the ACLOCAL_AMFLAGS line in the toplevel
> Makefile.am file?  The file is named exactly Makefile.am?  There is
> no whitespace before the word `ACLOCAL_AMFLAGS'?
> 
> Cheers,
> Ralf
> 


WBR Oleg V. Zhylin   address@hidden


      
____________________________________________________________________________________
Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ