Re: AM_*FLAGS and autoconf

Stepan and all, On 2005 Feb 22 , at 11.54, Stepan Kasal wrote: On Fri, Feb 18, 2005 at 04:30:13PM +, Norman Gray wrote: Sorry for taking a while to respond -- my list subscription had been suspended by lists.gnu.org _again_, because of the proportion of thus-delivered spam our boundary mailhost

Re: AM_*FLAGS and autoconf

Hello, On Fri, Feb 18, 2005 at 04:30:13PM +, Norman Gray wrote: > Sorry for taking a while to respond -- my list subscription had been > suspended by lists.gnu.org _again_, because of the proportion of > thus-delivered spam our boundary mailhosts had rejected. this is interesting, as there

Re: AM_*FLAGS and autoconf

Greetings, On 2005 Feb 16 , at 09:43, Alexandre Duret-Lutz wrote: Norman> Setting AM_CFLAGS is also out. The automake Norman> documentation talks of this being reserved for the Norman> author of Makefile.am, and doesn't mention autoconf at Norman> all. It's OK to AC_SUBST these if you like. M

Re: AM_*FLAGS and autoconf

>>> "Norman" == Norman Gray <[EMAIL PROTECTED]> writes: [...] Norman> Setting AM_CFLAGS is also out. The automake Norman> documentation talks of this being reserved for the Norman> author of Makefile.am, and doesn't mention autoconf at Norman> all. It's OK to AC_SUBST these if you like. Ma

AM_*FLAGS and autoconf

Greetings, How ought autoconf macros to pass flags, such as CFLAGS, to automake-generated makefiles? The automake FAQ answer doesn't answer all my questions about this. In my situation, I want to add -I and -L and ot