Re: how to prefix definitions in config.h

[Akim Demaille]

>>>>> "Clinton" == Clinton Roy <address@hidden> writes:

Clinton> Guido Draheim <address@hidden> writes:
>> ... the other problem is that the prefixing is not done during
>> reconfig, and in fact, the items in my ac-macro should be appended
>> to the config.status file, which I didn't bother to do so far, and
>> I didn't have enough time to figure it out.
Clinton> I think this is now the crux of the problem - how to get a
Clinton> command to be run by config.status every time config.h is
Clinton> generated - as we could use your prefixing code, my sed
Clinton> script, or Russ's awk script, depending on how we want to
Clinton> solve the installability problem.

Clinton> AC_CONFIG_COMMANDS seems like the right hook, but I'm unsure
Clinton> of the tag to use, I've seen `dummy', `default' (which
Clinton> actually seems to mean something to the case statement, eww)
Clinton> but I've had no success; I can get the command run by a
Clinton> manual invocation of configure, but not during
Clinton> reconfiguration.

I've asked this question several times.  I'm fine with having 2.54
released soon, with this question solved.  Paul, I would also like to
have your opinion.


My question is merely one of interface.

Currently

AC_INIT
AC_CONFIG_HEADERS(config.h)
AC_CONFIG_COMMANDS(config.h, [echo Hello, world])
AC_OUTPUT

is wrong (grr, it is not caught, I don't know why, but autoconf is
supposed to die on this).

My question is should we make this the normal way to hook a command,
or should we keep this invalid, and introduce

AC_INIT
AC_CONFIG_HEADERS(config.h)
AC_CONFIG_HOOKS(config.h, [echo Hello, world])
AC_OUTPUT

or something like that?