GNU bug report logs -
#12877
automake error: unrequested trace ''
Previous Next
Full log
View this message in rfc822 format
[+cc autoconf]
On 11/14/2012 07:45 AM, Sebastian Freundt wrote:
> Stefano Lattarini <stefano.lattarini <at> gmail.com> writes:
>
>> tags 12877 + moreinfo
>> thanks
>>
>> Hi Sebastian, thanks for the report.
>>
>> On 11/13/2012 11:30 AM, Sebastian Freundt wrote:
>>> shell> automake --version
>>> automake (GNU automake) 1.12.1
>>>
>>> autoreconf: running: automake --add-missing --copy --force-missing
>>> Use of uninitialized value $macro in exists at /home/freundt/usr/bin/automake line 5267, <GEN0> line 2.
>>> Use of uninitialized value $macro in concatenation (.) or string at /home/freundt/usr/bin/automake line 5267, <GEN0> line 2.
>>> automake: error: unrequested trace ''
>>> automake: Please contact <bug-automake <at> gnu.org>.
>>> at /home/freundt/usr/share/automake-1.12/Automake/Channels.pm line 662
>>> Automake::Channels::msg('automake', '', 'unrequested trace \'\'') called at /home/freundt/usr/share/automake-1.12/Automake/ChannelDefs.pm line 212
>>> Automake::ChannelDefs::prog_error('unrequested trace \'\'') called at /home/freundt/usr/bin/automake line 5267
>>> Automake::scan_autoconf_traces('configure.ac') called at /home/freundt/usr/bin/automake line 5533
>>> Automake::scan_autoconf_files() called at /home/freundt/usr/bin/automake line 8588
>>> autoreconf: automake failed with exit status: 29
>>>
>>> In project: https://quickplot.svn.sf.net/svnroot/quickplot/trunk
>>>
>> I cannot reproduce this failure with the latest automake release (1.12.4).
>> I've tried with both autoconf 2.69 and autoconf 2.65, just to be extra sure.
>>
>> Does the error disappear for you as well if you use automake 1.12.4?
>
> Ah, I found the culprit. But first off, the tag v1.12.4 isn't in the
> savannah git repo yet.
>
Yikes! Thank you very much for catching that, it's fixed now.
> (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?
> I recently populated this var in my shell setup because coreutils
> need it to work around some SysV quirks.
>
> So the workaround of the day (mostly a note to myself) is to unset
> POSIXLY_CORRECT temporarily when dealing with autotools.
>
> Cheers
> Sebastian
Thanks,
Stefano
This bug report was last modified 12 years and 252 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.