autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release candidate


From: Steve M. Robbins
Subject: Re: Release candidate
Date: Mon, 14 May 2001 11:14:54 -0400
User-agent: Mutt/1.3.17i

On Mon, May 14, 2001 at 04:57:57PM +0200, Peter Eisentraut wrote:
> Akim Demaille writes:
> 
> > | There is still the problem that autoconf mixes up variable assignments
> > | and macros.  This is up-to-the-minute CVS autoconf:
> > |
> > |         address@hidden configure.in
> > |         AC_INIT
> > |
> > |         AM_CFLAGS=foo
> > |         address@hidden
> > |         configure.in:3: error: undefined macro: AM_CFLAGS
> > |         address@hidden
> 
> Maybe it would be more helpful to write "possibly undefined macro: xxx",
> along with a description in the documentation, if you don't have one
> already.

Maybe I don't see what others see.  To me,

        FOO=bar

looks like a shell variable assignment.  I don't understand why
autoconf (apparently) treats this as a macro invocation.

Am I missing something fundamental here????
-S

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants




reply via email to

[Prev in Thread] Current Thread [Next in Thread]