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:
> > |
> > | steve@riemann{tmp}cat configure.in
> > | AC_INIT
> > |
> > | AM_CFLAGS=foo
> > | steve@riemann{tmp}autoconf
> > | configure.in:3: error: undefined macro: AM_CFLAGS
> > | steve@riemann{tmp}
>
> 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
