Ken Brown <kbrown <at> cornell.edu> writes: > Check setup.log.full. If that doesn't help, try running the script > manually to see what happens (most likely a fork failure requiring a > full rebase).
Well, if it's really a fresh install, the full rebase just has happened, so if there's still a fork problem it has to be BLODA. To the OP: if you're using any third-party anti-virus solution, please try if exempting the Cygwin install directory from the real-time and/or heuristic scans helps. In some cases you can re-enable those functions after a manual full scan, but you would likely run into the same problem again when the Cygwin packages get updated. Regards, Achim. -- 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