From: "Kaz Kylheku (Cygwin)" <743-406-3965@kylheku.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: Problem building cygwin-3_1_7-release tagged newlib.
Date: Sat, 10 Oct 2020 19:26:31 -0700 [thread overview]
Message-ID: <7ce744d853a7cbc5c52ce2b179325509@mail.kylheku.com> (raw)
In-Reply-To: <894dd3fb-f916-8f8a-da9a-c2003b06e8d1@cornell.edu>
On 2020-10-10 12:39, Ken Brown wrote:
> On 10/10/2020 3:22 PM, Kaz Kylheku (Cygwin) via Cygwin wrote:
>> 4896 | typedef struct _MEM_ADDRESS_REQUIREMENTS {
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> This looks like a clash between the installed toolchain header and the
>> one in the winsup tree?
>>
>> Is this a known problem?
>
> Yes. It was caused by a mingw-w64 update and was fixed in commit
> c1f7c4d1.
Much thanks for that; it got past this stumbling block. After that there
were
a bunch of GCC-10 fixes I had to find and cherry pick, and it built.
prev parent reply other threads:[~2020-10-11 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 19:22 Kaz Kylheku (Cygwin)
2020-10-10 19:39 ` Ken Brown
2020-10-11 2:26 ` Kaz Kylheku (Cygwin) [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=7ce744d853a7cbc5c52ce2b179325509@mail.kylheku.com \
--to=743-406-3965@kylheku.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).