From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: arnold@skeeve.com
Subject: Re: Latest 64 bit cygwin miscompiles gawk master
Date: Wed, 19 Apr 2017 18:25:00 -0000 [thread overview]
Message-ID: <20170419150409.GA27154@calimero.vinschen.de> (raw)
In-Reply-To: <201704191432.v3JEWEL9023030@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Hi Arnold,
On Apr 19 08:32, arnold@skeeve.com wrote:
> Hi.
>
> I just did a fresh install of the 64 bit cygwin on a new Windows 10
> computer. I am trying to build gawk from git master and getting
> failures. It looks like something is being miscompiled in the NODE
> union. Compiler is GCC 5.4. I have no problems with this compiler
> on Ubuntu 16 or with GCC 4.9 on an older 64 bit cygwin.
>
> Also, when running configure, there are a lot of errors about not
> being able to remove conftest.exe, device or resource busy, which I do
> not get on the older Cygwin.
>
> Repeat by
>
> git clone http://git.savannah.gnu.org/r/gawk.git
> cd gawk
> ./bootstrap.sh && ./configure && make -j && make check
>
> Watch several of the checks crash and burn
No, I don't. I just ran the exact sequence as above on a x86_64 Windows
10 machine with Cygwin 2.8.0 and gcc 5.4.0 and "ALL TESTS PASSED".
Sure you're not suffering a BLODA problem?
See https://cygwin.com/faq/faq.html#faq.using.bloda
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-04-19 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 15:32 arnold
2017-04-19 18:25 ` Corinna Vinschen [this message]
2017-04-19 23:01 ` arnold
2017-04-21 0:10 ` arnold
2017-04-21 14:06 ` Corinna Vinschen
2017-04-21 0:11 ` cyg Simple
2017-04-19 21:47 arnold
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=20170419150409.GA27154@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=arnold@skeeve.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).