Re: Setting ACLOCAL_AMFLAGS with ':=' vs '='

On 2014-09-18 09:36 +0100, R. Diez wrote: > If I add this line to my Makefile.am (and I make sure that the 'm4' > subdir is created beforehand), then it works as intended: > > ACLOCAL_AMFLAGS = -I m4 > > However, if I use this syntax: > > ACLOCAL_AM

Setting ACLOCAL_AMFLAGS with ':=' vs '='

Hallo there: If I add this line to my Makefile.am (and I make sure that the 'm4' subdir is created beforehand), then it works as intended: ACLOCAL_AMFLAGS = -I m4 However, if I use this syntax: ACLOCAL_AMFLAGS := -I m4 Then I get the following warning: libtoolize: Consider

Re: need to set ACLOCAL_AMFLAGS along with AC_CONFIG_MACRO_DIR

any rate, it seems like maintaining ACLOCAL_AMFLAGS in > > Makefile.am is redundant > > For simple setups, yes. How common are non-simple setups? I don't > know for sure, but I would guess any package with more than a > couple of configure scripts might need more than one

Re: ACLOCAL_AMFLAGS problems

Hello Ruben, Apologies for the delay, I must have missed this somehow: <http://thread.gmane.org/gmane.comp.sysutils.automake.general/8983> * Ruben Henner Zilibowitz wrote on Tue, Dec 18, 2007 at 01:59:44PM CET: > I have run into a problem where the following line: > ACLOCAL_AMFLAGS

ACLOCAL_AMFLAGS problems

I have run into a problem where the following line: ACLOCAL_AMFLAGS = -I m4 in the top level Makefile.am causes "make dist" to fail. Eg: Ruben-Henner-Zilibowitzs-iMac:hello rhz$ make dist { test ! -d hello-0.1 || { find hello-0.1 -type d ! -perm -200 -exec chmod u+w {} ';'

Re: ACLOCAL_AMFLAGS looks like no effect on make

> 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 A

Re: ACLOCAL_AMFLAGS looks like no effect on make

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 t

ACLOCAL_AMFLAGS looks like no effect on make

Hi, 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

Re: Including local macros with ACLOCAL_AMFLAGS

On Wednesday 16 March 2005 08:12, Ralf Wildenhues wrote: > Oh, or are you invoking aclocal directly? Then you should do > aclocal -I m4 > > ACLOCAL_AMFLAGS are only respected by the rebuilding rules put in > Makefile.in and by autoreconf. Thanks for your help, Ralf. I was i

Re: Including local macros with ACLOCAL_AMFLAGS

Hi Rohnny, * Rohnny Moland wrote on Tue, Mar 15, 2005 at 10:46:13PM CET: > > I am trying to include my own local m4 macros to a project. In the automake > documentation I read that the preferred way to do this would be to add the > following line to the Makefile.am file: > &g

Including local macros with ACLOCAL_AMFLAGS

Hello, I am trying to include my own local m4 macros to a project. In the automake documentation I read that the preferred way to do this would be to add the following line to the Makefile.am file: ACLOCAL_AMFLAGS = -I m4 ..where m4 is the directory where I put my macros. Unfortunately when

Re: ACLOCAL_AMFLAGS

Hello, Ralf! > $(ACLOCAL_M4): configure.in \ > ./../aclocal/x.m4 \ > > AFAIS, the "strip "./"" from this patch is to blame for this: You are right, it's my bug. I'll fix it soon. Thank you. Regards, Pavel Roskin

ACLOCAL_AMFLAGS

ACLOCAL_AMFLAGS are broken w/ cvs/automake Example: Given this excerpt of a sourcetree: aclocal/x.m4 a/b/configure.in a/b/Makefile.am cat a/b/Makefile.am .. ACLOCAL_AMFLAGS = -I ../../aclocal .. The generated Makefile.in will contain .. $(ACLOCAL_M4): configure.in