Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes: > Hi Eric,
Hi Ralf, > > touch configure.ac then attempt a parallel make on cygwin: > > Do you see these failures with Automake 1.10.2 also? I'll start checking that, but thought I'd at least give a first round of replies. > Which Autoconf versions are you using? This was with bleeding edge autoconf.git, but as part of downgrading to automake 1.10.2, I'll also drop back to autoconf 2.63. > Have you seen them on systems other than Cygwin? > How old is this Cygwin version? Haven't tested other systems yet. This was on cygwin 1.7 (still in beta), so it could very well be a cygwin problem, although I am pretty sure that I have also seen it on the latest stable cygwin 1.5.x. I'll confirm. > Which Perl version do you have installed? perl 5.10.0, as shipped pre-built for cygwin (same perl for both cygwin 1.5 and 1.7). > Which file system does this happen on? NTFS. > > autoconf and automake are intended to be able to run in parallel, that's > what XFile::lock and its call in autom4te is for. > > The above looks like XFile::lock fails to do its work. We should have a > test that ensures that, in either Autoconf or Automake. Indeed it is possible that some of the cygwin 1.7 improvements might be the cause of XFile::lock behaving differently; if there is a way to trim this down to a smaller test case, the cygwin developers would likely be able to investigate it. -- Eric Blake
