From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Errors using configure when building packages
Date: Fri, 14 Oct 2016 22:58:00 -0000 [thread overview]
Message-ID: <7daa34c2-b176-c802-d5ae-a87745a69830@cornell.edu> (raw)
In-Reply-To: <ECD9CD6C7B163F4882AB10BC135BF588333441EA@DE08EX3006.global.ds.honeywell.com>
On 10/14/2016 1:46 PM, Sinkler, Wharton wrote:
> I've got a new Cygwin installation on Win7, which has issues with configure, the first step of building packages from source (I've seen this with ImageMagick, libtiff and others so it's not specific to the package I'm installing).
>
> It seems to sporadically be unable to remove a file 'conftest.exe' which is compiled in the tests within configure. This shows up during configure as:
>
> rm: cannot remove 'conftest.exe': Device or resource busy
>
> The configure will then fail completely when this causes a critical test to fail.
>
> I suspect that this might have something to do with slowness to release an in-use file (the conftest.exe) in the Win7 operating system. I've searched the archives and don't see this exact issue showing up in previous posts. Have others experienced this problem? Is there a fix which will allow me to complete building these packages?
Do you have security software installed that might be interfering with
Cygwin?
Ken
--
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-14 20:23 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 [this message]
2016-10-17 20:20 ` cyg Simple
2016-10-17 22:57 ` Sinkler, Wharton
2016-10-18 14:34 ` Brian Inglis
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=7daa34c2-b176-c802-d5ae-a87745a69830@cornell.edu \
--to=kbrown@cornell.edu \
--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).