This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: multilib and Makefile regeneration

From: Paolo Bonzini <bonzini at gnu dot org>
To: gcc at gcc dot gnu dot org, autoconf at gnu dot org, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
Date: Mon, 31 Aug 2009 23:53:17 +0200
Subject: Re: multilib and Makefile regeneration
References: <20090831211118.GE21485@gmx.de>

On 08/31/2009 11:11 PM, Ralf Wildenhues wrote:

The easiest for now would be (3), the coolest, most difficult and
probably most dangerous one would be (2).  Something like
   AC_CONFIG_FILES_COMMANDS(some/Makefile, more-user-commands,
                            [more-init-cmds])

but then the order of issuing this and the respective
   AC_CONFIG_FILES(some/Makefile)

would be significant. I don't see any way to avoid this.

You could specify that AC_CONFIG_FILES comes first, and *_COMMANDS occurrences come later in the order that appears in the source (and do nothing unless the corresponding AC_CONFIG_FILES exists).

The simplest implementation would amount to two m4_append (actually one m4_append plus one _AC_CONFIG_COMMANDS_INIT) in AC_CONFIG_FILES_COMMANDS, and an m4_ifdef in _AC_CONFIG_REGISTER_DEST.

Paolo

References:
- multilib and Makefile regeneration
  - From: Ralf Wildenhues

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]