From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Errors using configure when building packages
Date: Tue, 18 Oct 2016 14:34:00 -0000 [thread overview]
Message-ID: <7e395da4-f9e1-8ca1-11f5-68002f05a754@SystematicSw.ab.ca> (raw)
In-Reply-To: <ECD9CD6C7B163F4882AB10BC135BF588333462F0@DE08EX3006.global.ds.honeywell.com>
On 2016-10-17 16:54, Sinkler, Wharton wrote:
> Yes that did it. The problem was definitely caused by virus scan -
> McAfee. Not sure why, but excluding the folder from on-access scanner
> did not get rid of the error. Only by completely disabling Access
> Protection and On-Access Scanner in the McAfee console was I able to
> complete the configure script for ImageMagick on my Cygwin
> installation.
> Thanks for the help and hope this will help others who encounter this
> problem.
What helps your system even more is deinstalling McAfee as it seems to
take a really safe but really dumb approach which slows Cygwin and Windows
drastically, unless you add a LOT of exclusions.
Then you can enable Windows Defender, and download and install Microsoft
Security Essentials if you are still on Win 7/8: Win 10 Defender includes
MSE functions so it is not required there.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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-10-18 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 20:15 Sinkler, Wharton
2016-10-14 22:58 ` Ken Brown
2016-10-17 20:20 ` cyg Simple
2016-10-17 22:57 ` Sinkler, Wharton
2016-10-18 14:34 ` Brian Inglis [this message]
2016-10-17 19:44 ` Linda Walsh
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=7e395da4-f9e1-8ca1-11f5-68002f05a754@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).