Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-08 Thread Eric Blake
On 10/01/2010 10:35 AM, Eric Blake wrote: That assumes, of course, that I can easily fix the regression of AS_PUSH_VAR accepting a var-name with = in it ;) It may not be today, but it's certainly on my list of things to tackle during the first week of October. Oops - it's the 8th; I missed my

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-02 Thread Paolo Bonzini
On Fri, Oct 1, 2010 at 18:35, Eric Blake ebl...@redhat.com wrote: On 10/01/2010 10:03 AM, Paolo Bonzini wrote: I think the correct answer is do whatever it has been doing until 2.67. :) And the testsuite should be updated to have the appropriate coverage, and I want a pony. I can't promise

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Paolo Bonzini
On 09/27/2010 07:46 PM, Eric Blake wrote: I was able to reduce the problem to the following trivial case: --8--cut here--8-- AC_DEFUN([MY_MACRO], [AS_VAR_PUSHDEF([VAR],[prefix_$1]) dnl This is the version used by AX_CFLAGS_GCC_OPTION. dnl I

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Eric Blake
On 10/01/2010 06:51 AM, Paolo Bonzini wrote: On 09/27/2010 07:46 PM, Eric Blake wrote: I was able to reduce the problem to the following trivial case: --8--cut here--8-- AC_DEFUN([MY_MACRO], [AS_VAR_PUSHDEF([VAR],[prefix_$1]) dnl This is the

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Eric Blake
On 10/01/2010 09:07 AM, Paolo Bonzini wrote: On 10/01/2010 03:57 PM, Eric Blake wrote: Either way, the name of the indirect variable being assigned is $prefix_a_b, whether you use pre- or post-2.67. Why is 'a=b' being passed instead of 'a_b' in the first place? I'd need to see more context of

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Paolo Bonzini
On 10/01/2010 05:11 PM, Eric Blake wrote: On 10/01/2010 09:07 AM, Paolo Bonzini wrote: On 10/01/2010 03:57 PM, Eric Blake wrote: Either way, the name of the indirect variable being assigned is $prefix_a_b, whether you use pre- or post-2.67. Why is 'a=b' being passed instead of 'a_b' in the

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Eric Blake
On 10/01/2010 10:03 AM, Paolo Bonzini wrote: I think the correct answer is do whatever it has been doing until 2.67. :) And the testsuite should be updated to have the appropriate coverage, and I want a pony. I can't promise the pony :) But given the arguments that have been raised on this

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-10-01 Thread Ben Pfaff
Paolo Bonzini bonz...@gnu.org writes: On 10/01/2010 03:57 PM, Eric Blake wrote: Either way, the name of the indirect variable being assigned is $prefix_a_b, whether you use pre- or post-2.67. Why is 'a=b' being passed instead of 'a_b' in the first place? I'd need to see more context of

Re: Bug #593838: AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable

2010-09-27 Thread Eric Blake
On 09/25/2010 12:22 PM, Ben Pfaff wrote: retitle 593838 AX_CFLAGS_GCC_OPTION misuses AS_VAR_PUSHDEF variable reassign 593838 autoconf-archive thanks Jerome BENOITjgm...@rezozer.net initially reported that AX_CFLAGS_GCC_OPTION(-std=c99) fails with Autoconf 2.67. Vincent Bernatber...@debian.org