From: Ken Brown <kbrown@cornell.edu>
To: "Kaz Kylheku (Cygwin)" <743-406-3965@kylheku.com>, cygwin@cygwin.com
Subject: Re: Problem building cygwin-3_1_7-release tagged newlib.
Date: Sat, 10 Oct 2020 15:39:25 -0400 [thread overview]
Message-ID: <894dd3fb-f916-8f8a-da9a-c2003b06e8d1@cornell.edu> (raw)
In-Reply-To: <bc891064e524067b663bfdaaf7ee0995@mail.kylheku.com>
On 10/10/2020 3:22 PM, Kaz Kylheku (Cygwin) via Cygwin wrote:
> Hi,
>
> I'm trying to build the 3.1.7 tagged newlib. It runs into this problem:
>
> c++wrap -O2 -g -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall
> -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0
> -MMD -Wimplicit-fallthrough=5 -Werror -fmerge-constants -ftracer -c -o
> _cygwin_crt0_common.o ../../.././winsup/cygwin/lib/_cygwin_crt0_common.cc
> In file included from ../../.././winsup/cygwin/winsup.h:83,
> from ../../.././winsup/cygwin/lib/_cygwin_crt0_common.cc:9:
> ../../.././winsup/cygwin/winlean.h:104:16: error: redefinition of 'struct
> _MEM_ADDRESS_REQUIREMENTS'
> 104 | typedef struct _MEM_ADDRESS_REQUIREMENTS
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/include/w32api/minwindef.h:163,
> from /usr/include/w32api/windef.h:9,
> from /usr/include/w32api/windows.h:69,
> from ../../.././winsup/cygwin/winlean.h:56,
> from ../../.././winsup/cygwin/winsup.h:83,
> from ../../.././winsup/cygwin/lib/_cygwin_crt0_common.cc:9:
> /usr/include/w32api/winnt.h:4896:18: note: previous definition of 'struct
> _MEM_ADDRESS_REQUIREMENTS'
> 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.
Ken
next prev parent reply other threads:[~2020-10-10 19:39 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 [this message]
2020-10-11 2:26 ` Kaz Kylheku (Cygwin)
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=894dd3fb-f916-8f8a-da9a-c2003b06e8d1@cornell.edu \
--to=kbrown@cornell.edu \
--cc=743-406-3965@kylheku.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).