DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A8D223857C50
To: Ken Brown <kbrown@cornell.edu>
Subject: Re: Problem building =?UTF-8?Q?cygwin-=33=5F=31=5F=37-release=20t?=
 =?UTF-8?Q?agged=20newlib=2E?=
MIME-Version: 1.0
Date: Sat, 10 Oct 2020 19:26:31 -0700
In-Reply-To: <894dd3fb-f916-8f8a-da9a-c2003b06e8d1@cornell.edu>
References: <bc891064e524067b663bfdaaf7ee0995@mail.kylheku.com>
 <894dd3fb-f916-8f8a-da9a-c2003b06e8d1@cornell.edu>
Message-ID: <7ce744d853a7cbc5c52ce2b179325509@mail.kylheku.com>
User-Agent: Roundcube Webmail/0.9.2
Precedence: list
From: "Kaz Kylheku \(Cygwin\) via Cygwin" <cygwin@cygwin.com>
Reply-To: "Kaz Kylheku \(Cygwin\)" <743-406-3965@kylheku.com>
Cc: cygwin@cygwin.com
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

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.

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple