Eric Blake <ebb9 <at> byu.net> writes: > > 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. >
Indeed, this snippet from the cygwin 1.7 release notes[1] is telling: - File locking is now advisory, not mandatory anymore. The fcntl(2) and the new lockf(2) APIs create and maintain locks with POSIX semantics, the flock(2) API creates and maintains locks with BSD semantics. POSIX and BSD locks are independent of each other. [1] http://cygwin.com/1.7/cygwin-ug-net/ov-new1.7.html
