On Sat, 23 Feb 2008, Chris Pickett wrote:
Note that I've had autoconf working on this system for about a year,
this only started happening recently... something changed, somewhere.
I think that it is reasonable to initially assume that something changed
in autoconf which aggravates this problem somehow. It may be that there
is a race condition in the autoconf script which causes a locked file to
be removed while an autoconf-initiated process is still using it, and
that this sub-process then hangs.