Bug 210653 - aclocal triggers a warning about an uninitialized variable
Summary: aclocal triggers a warning about an uninitialized variable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: autoconf
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: 210668
TreeView+ depends on / blocked
 
Reported: 2006-10-13 15:39 UTC by Stepan Kasal
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: autoconf-2.59-12
Clone Of:
Environment:
Last Closed: 2006-11-02 11:11:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
a fix (1.98 KB, patch)
2006-10-13 16:12 UTC, Stepan Kasal
no flags Details | Diff

Description Stepan Kasal 2006-10-13 15:39:25 UTC
With perl-5.8.8-10 on i686, I see a warning whenever I run aclocal:

Use of uninitialized value in concatenation (.) or string at
/usr/share/autoconf/Autom4te/XFile.pm line 229.

The message does not appear with perl-5.8.8-8 on x86_64.

Lines 216-229 are:
sub lock
{
  my ($fh, $mode) = @_;
  # [...]
  if (!flock ($fh, $mode)

The message comes from the call to "lock" in /usr/bin/autom4te.
(autom4te is executed by aclocal.)

Steps to reproduce:
wget http://ftp.gnu.org/pub/gnu/gawk/gawk-3.1.5.tar.bz2
tar xjf gawk-3.1.5.tar.bz2
cd gawk-3.1.5
aclocal

Comment 1 Stepan Kasal 2006-10-13 16:12:47 UTC
Created attachment 138446 [details]
a fix

The message is triggeted by this: $ENV{'MAKEFLAGS'}

The issue is fixed in autoconf-2.60, where is this patch taken from.

Comment 2 Stepan Kasal 2006-10-13 17:05:43 UTC
There is one factor which I missed previously: the message appears only when
working in a NFS mounted directory.
But then it is triggered by every call to autoconf, automake, autoheader, or
aclocal.

Comment 3 Karsten Hopp 2006-11-02 11:11:11 UTC
fixed in FC6, Rawhide and RHEL-5 with autoconf-2.59-12


Note You need to log in before you can comment on or make changes to this bug.