From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: race issue on configure
Date: Tue, 10 Jan 2017 20:44:00 -0000 [thread overview]
Message-ID: <103d3f6d-9944-6b5a-69e3-623281e4059f@SystematicSw.ab.ca> (raw)
In-Reply-To: <4ce03edc-39e8-7d29-8c2d-a7d09259fde7@gmail.com>
On 2017-01-10 07:07, cyg Simple wrote:
> On 1/10/2017 9:02 AM, Marco Atzeri wrote:
>> On 10/01/2017 14:55, cyg Simple wrote:
>>> On 1/10/2017 5:24 AM, Marco Atzeri wrote:
>>>> I am noticing race problems during configure tests, on both 32
>>>> and 64 bit builds.
>>>> The effect is a random failing test as conftest.exe can not be
>>>> access by the linker.
>>> This is caused by your AV scanning the recently created
>>> conftest.exe and the fact that since the AV has it open it cannot
>>> be deleted and a new one created. Instruct your AV to ignore your
>>> work directory.
>> It is instructed to do so by long time within the limit of
>> corporate settings...
> Maybe new policy enforcement by corporate. The only time I've seen
> this issue is related to AV having the conftest.exe file open.
May also be opened by background Windows Search/Cortana/... for
indexing and/or that may be causing it to be rescanned - I had
similar problems solved after disabling those search services.
Run Resource Monitor from bottom of Task Manager/Performance tab
and watch Disk Activity pane ordered by File for interfering
processes, and kill them if safe, disable if standalone service.
If it's svchost or AV process, search if you can bypass or
disable those actions or directories, or request a custom policy
for your userid or systems as it's interfering with work.
Security interfering with work tends to get fixed to allow work
to be done: a lot of security policies interfere with development
work, and have to be bypassed.
It would be better and easier for all if they packaged the
security policy bypasses with the development tool installs.
I've had to jump thru a few corporate hoops to keep things kosher
and simplify updates and use: it's often easy these days for
developers to add zero cost, email/web supported packages to
corporate tracking systems with yourself as in-house support:
YMMV. ;^>
--
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
prev parent reply other threads:[~2017-01-10 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 10:24 Marco Atzeri
2017-01-10 13:56 ` cyg Simple
2017-01-10 14:03 ` Marco Atzeri
2017-01-10 14:07 ` cyg Simple
2017-01-10 20:44 ` Brian Inglis [this message]
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=103d3f6d-9944-6b5a-69e3-623281e4059f@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).