Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

2012-11-14 Thread Sebastian Freundt 
"Stefano Lattarini"  writes:

> tags 12877 - moreinfo
> tags 12877 notabug
> close 12877
> thanks
>
> On 11/14/2012 12:09 PM, Sebastian Freundt wrote:
>>
>> "Stefano Lattarini"  writes:
>>> 
>>> On 11/14/2012 07:45 AM, Sebastian Freundt wrote:

 (GNU) m4 when being called with the variable POSIXLY_CORRECT behaves
 differently as all GNU extensions will be suppressed.

>>> Modern autoconf versions used with modern GNU m4 versions should pass
>>> the latter the '-g' option, so that the POSIXLY_CORRECT variable does
>>> not have any effect on the behaviour of GNU m4.  Which versions of
>>> autoconf and m4 are you using?
>>>
>> 
>> freundt@clyde:pts/30:~> autoconf --version
>> autoconf (GNU Autoconf) 2.69
>> Copyright (C)  Free Software Foundation, Inc.
>> License GPLv3+/Autoconf: GNU GPL version 3 or later
>> , 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> 
>> Written by David J. MacKenzie and Akim Demaille.
>>
> Modern enough I'd say :-)
>
>> freundt@clyde:pts/30:~> m4 --version
>> m4 (GNU M4) 1.9a.574-8613
>> Copyright (C) 2010 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> .
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> 
>> Written by Rene' Seindal, Gary V. Vaughan, and Eric Blake.
>> 
> Ha, here lies the problem.  According to the m4 NEWS file, the '-g' option
> has only been introduced in version 1.4.12.  I'd suggest you to update
> your m4 installation to the latest if possible.
>
> In the meanwhile, I'm closing this report, since we've determined your
> problem is not due to an automake or aclocal bug.

Yes, I will report this issue to the m4 guys.  
1.9a has the -g switch and is newer than 1.4 anyway.

Cheers
Sebastian

___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

2012-11-14 Thread Eric Blake 
[adding bug-m4]

On 11/14/2012 04:09 AM, Sebastian Freundt wrote:
>>> (GNU) m4 when being called with the variable POSIXLY_CORRECT behaves
>>> differently as all GNU extensions will be suppressed.
>>>
>> Modern autoconf versions used with modern GNU m4 versions should pass
>> the latter the '-g' option, so that the POSIXLY_CORRECT variable does
>> not have any effect on the behaviour of GNU m4.  Which versions of
>> autoconf and m4 are you using?
>>

> freundt@clyde:pts/30:~> m4 --version
> m4 (GNU M4) 1.9a.574-8613

Alas, there's your problem.  You self-built from m4.git, but built from
the master (experimental) branch instead of branch-1.4 (stable
releases); unfortunately, the experimental branch is just that, and
doesn't yet play nicely with autoconf.

I should probably find a way to reject any m4 version at autoconf's
configure time if it doesn't support GNU extensions; meanwhile, I should
also find time to fix m4.git to make the experimental branch not regress
in relation to released m4.

-- 
Eric Blake   ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature
___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

2012-11-14 Thread Stefano Lattarini 
On 11/14/2012 12:24 PM, Sebastian Freundt wrote:
> "Stefano Lattarini"  writes:
> 
> Yes, I will report this issue to the m4 guys.  
> 1.9a has the -g switch and is newer than 1.4 anyway.
>
Oh, sorry, I has misread the version number as "1.4.9a" *blush*!

I agree a report to the m4 list might be a good move.  But consider
that the 2.0 m4 release has been put in the back burner "until further
notice", so I'd still suggest you to only employ m4 versions in the
1.4.x series for the moment being; especially for any production use.

Regards,
  Stefano

___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

2012-11-14 Thread Stefano Lattarini 
tags 12877 - moreinfo
tags 12877 notabug
close 12877
thanks

On 11/14/2012 12:09 PM, Sebastian Freundt wrote:
>
> "Stefano Lattarini"  writes:
>> 
>> On 11/14/2012 07:45 AM, Sebastian Freundt wrote:
>>>
>>> (GNU) m4 when being called with the variable POSIXLY_CORRECT behaves
>>> differently as all GNU extensions will be suppressed.
>>>
>> Modern autoconf versions used with modern GNU m4 versions should pass
>> the latter the '-g' option, so that the POSIXLY_CORRECT variable does
>> not have any effect on the behaviour of GNU m4.  Which versions of
>> autoconf and m4 are you using?
>>
> 
> freundt@clyde:pts/30:~> autoconf --version
> autoconf (GNU Autoconf) 2.69
> Copyright (C)  Free Software Foundation, Inc.
> License GPLv3+/Autoconf: GNU GPL version 3 or later
> , 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by David J. MacKenzie and Akim Demaille.
>
Modern enough I'd say :-)

> freundt@clyde:pts/30:~> m4 --version
> m4 (GNU M4) 1.9a.574-8613
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later .
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by Rene' Seindal, Gary V. Vaughan, and Eric Blake.
> 
Ha, here lies the problem.  According to the m4 NEWS file, the '-g' option
has only been introduced in version 1.4.12.  I'd suggest you to update
your m4 installation to the latest if possible.

In the meanwhile, I'm closing this report, since we've determined your
problem is not due to an automake or aclocal bug.

HTH,
  Stefano

___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf