David Stacey wrote:
I think what you're seeing here is what we term a BLODA - some non-Cygwin application interfering with a Cygwin application. In your case, if you're not running a native Windows svn client then anti-virus is top of the suspect list. I know you claim that you have used MSE for years, but anti-virus tools update very frequently, and their behaviour can (and does) change. See the following link, under "File access problems": http://cygwin.com/faq/faq.html#faq.using.blodaYour best bet is to either disable or tune the anti-virus tool so that it doesn't scan the '.svn' directory inside your working copy. If you do this, does the check out complete successfully? If you are not able to try this, can you get svn to recover? Try these two commands in succession: $ svn cleanup <directory> $ svn update <directory> Does the check out complete (or at least get a little further)? I've taken a look at the cygcheck output that you attached and it seems to be OK. So unless anyone else on this list can provide further insight, it really looks as if a third party (probably your anti-virus) is locking the 'wc.db' file whilst svn is trying to update it - and there's not much we can do about that.
As suggested here, http://gcc.gnu.org/ml/fortran/2013-09/msg00067.html there is a git mirror which allows to download the fortran-dev branch.. Thanks, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
