On Jan 24 17:46, Alexander Sotirov wrote: > Larry Hall (Cygwin) wrote: > > That's a Windowsism. You should see better results with a recent snapshot: > > > > <http://cygwin.com/snapshots/> > > > > It would be great if you tested your case with a snapshot and report back > > your findings. > [...] > It looks like the bug is a result of a change that happened between the > 1.5.19-4 > release from Jan 20 and the snapshot from Mar 22.
It's not exactly a bug. The reason for this is a change in the opendir/readdir/closedir implementation. The old implementation used Win32 functions in a way which opened a handle to the directory only when the first readdir has been called. The new implementation opens the handle already on opendir. Make calls opendir on the foo/bar directory as a result of the implicit rule, but not readdir, so there was no open handle in the old implementation, but there is an open handle now. I have a new implementation of unlinking files which should help here, too. I'll look into using this method for rmdir as well. However, this will not be available in the upcoming 1.5.24 release. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
