From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: New cygwin install hanging on postinstall
Date: Thu, 21 Jan 2016 13:18:00 -0000 [thread overview]
Message-ID: <loom.20160121T085819-962@post.gmane.org> (raw)
In-Reply-To: <56A02A77.6050409@cornell.edu>
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
next prev parent reply other threads:[~2016-01-21 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:34 KARR, DAVID
2016-01-21 5:42 ` Stephen John Smoogen
2016-01-21 19:09 ` KARR, DAVID
2016-01-21 21:29 ` Ken Brown
2016-01-21 21:51 ` Achim Gratz
2016-01-22 3:12 ` KARR, DAVID
2016-01-22 7:30 ` David Stacey
2016-01-22 17:32 ` Andrey Repin
2016-01-22 18:50 ` KARR, DAVID
2016-01-22 20:07 ` Mark Geisert
2016-01-22 20:14 ` Andrey Repin
2016-01-21 8:02 ` Ken Brown
2016-01-21 13:18 ` Achim Gratz [this message]
2016-01-21 21:17 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160121T085819-962@post.gmane.org \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).