Re: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument

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

 



"David Byron" <dbyron@xxxxxxxxxx> writes:

> The subject says it all.  I'm getting a warning message running autoreconf
> that I've never seen before.  Here's the full output:
>
> $ autoreconf -fvi
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal --force -I m4
> autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
[...]
> I see these warnings on an HP-UX 11 machine.

Looks like your perl does not properly implement flock.  See sub lock in
Autom4te/XFile.pm.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@xxxxxxx
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux