RE: AM_CONDITIONAL and += macros

[Francis Michel <francis dot michel at trisignal dot com>]

Why does the latest version of autoconf (2.52.5) and automake (1.5b-1) de
not require the same
macro that declares the file where AC_OUTPUT define C preprocessor macros.

The autoconf manual describes AC_CONFIG_HEADER macro and the automake manual
describes that
automake requires AM_CONFIG_HEADER. I remember that previous versions of the
scripts were OK
with that process.

Defining AM_CONFIG_HEADER will result in a problem at the configure process
since the macro
won't be found by autoconf. Defining AC_CONFIG_HEADER result in problems
with automake when 
generating the final makefile.

Can anyone help me out here with a workaround?

Thanks a lot

Francis Michel
-----Original Message-----
From: Jean-Bernard Delva [mailto:jb@trisignal.com]
Sent: 4 février, 2002 16:12
To: automake@gnu.org
Cc: francis.michel@trisignal.com; steve.goddyn@trisignal.com
Subject: AM_CONDITIONAL and += macros


Why is it that using '+=' inside an 'if' with automake causes errors?

Here is an example makefile.am illustrating the offending behavior:

DUMMY = a

if SOME_CONDITION
DUMMY += b
endif

---
This prompts automake to produce the following error:
Makefile.am:1: DUMMY was already defined in condition TRUE, which implies 
condition SOME_CONDITION

   DUMMY (User, where = 1) +=
   {
     TRUE => a
   }

Since 'DUMMY' is previously unconditionally defined, I don't see a way that 
it could cause an error later. Automake should allow the definition.

I know that Automake likes to collect all definitions of a particular macro 
into a single definition. Couldn't Automake make an exception with '+=' in 
conditionals?

Can anyone point to me what I am doing wrong or provide a workaround?

Thank you,

Jean-Bernard Delva