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]

To: autoconf@xxxxxxx
Subject: Re: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
From: Harlan Stenn <stenn@xxxxxxxxxxx>
Date: Mon, 12 Mar 2007 04:50:01 +0000
In-reply-to: Message from "David Byron" <dbyron@xxxxxxxxxx> of "Sun, 11 Mar 2007 21:07:54 MST." <030b01c7645c$02953450$8b01a8c0@LLEVAR>

David,

Just a guess here.  What are the ownership/perms of the autom4te.cache
dir and the /requests file in there?

H


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

Follow-Ups:
- RE: autoreconf warning message: autom4te: cannot lockautom4te.cache/requests with mode 2: Invalid argument
  - From: David Byron

References:
- autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
  - From: David Byron

Prev by Date: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
Next by Date: Re: How to avoid warning: "PACKAGE_NAME" redefined
Previous by thread: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
Next by thread: RE: autoreconf warning message: autom4te: cannot lockautom4te.cache/requests with mode 2: Invalid argument
Index(es):
- Date
- Thread

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

Powered by Linux