bug-autoconf
[Top][All Lists]
Advanced

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

Re: bad m4 quotation?


From: Ralf Wildenhues
Subject: Re: bad m4 quotation?
Date: Tue, 4 Apr 2006 10:53:59 +0200
User-agent: Mutt/1.5.11

Hi Noah,

* Noah Misch wrote on Sun, Apr 02, 2006 at 08:32:17PM CEST:
> 
> Notice that this sort of first argument to AC_CONFIG_{FILES,HEADERS} has not
> worked, but that AC_CONFIG_COMMANDS had accepted such constructs, and that CVS
> now treats AC_CONFIG_COMMANDS like the others (as of a 2005-07-25 change).

Agreed.

> (Side note: the removal of double quotes is suspicious; it appears to change
> behavior for weird tag names.  This may not matter too much.)

Let's not worry about that until we get a report to this end.

> Long term, we might want to diagnose and forbid AC_CONFIG_<FOO>S tags 
> containing
> characters special to the shell, which would also catch macro calls.  For now,
> let us fix this regression by treating the first argument to 
> AC_CONFIG_COMMANDS
> as we did in Autoconf 2.59:

Yes.  Please apply, and thanks for analyzing and debugging this!

Cheers,
Ralf

> 2006-04-02  Noah Misch  <address@hidden>
> 
>       * lib/autoconf/status.m4 (_AC_CONFIG_FOOS): Do not append normalized
>       TAGS to ac_config_<foo>s.
>       (AC_CONFIG_FILES, AC_CONFIG_HEADERS, AC_CONFIG_LINKS): Do so here.
>       (AC_CONFIG_COMMANDS): Append NAME to ac_config_commands without
>       normalizing it, consistent it with previous releases.
>       * tests/torture.at (Macro calls in AC_CONFIG_COMMANDS tags): New test.





reply via email to

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