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
--
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
