From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: race issue on configure
Date: Tue, 10 Jan 2017 13:56:00 -0000 [thread overview]
Message-ID: <f3d94918-c14d-0324-6e0d-0c2c36ab34d3@gmail.com> (raw)
In-Reply-To: <599a2afe-7abe-512a-b3c4-2f9a738a9855@gmail.com>
On 1/10/2017 5:24 AM, Marco Atzeri wrote:
> Hi,
>
> 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 directlry.
--
cyg Simple
--
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:[~2017-01-10 13:56 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 [this message]
2017-01-10 14:03 ` Marco Atzeri
2017-01-10 14:07 ` cyg Simple
2017-01-10 20:44 ` Brian Inglis
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=f3d94918-c14d-0324-6e0d-0c2c36ab34d3@gmail.com \
--to=cygsimple@gmail.com \
--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).