From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Updated: w32api-{headers,runtime}-8.0.0-1 (x86/x86_64)
Date: Tue, 22 Sep 2020 16:10:50 -0600 [thread overview]
Message-ID: <9a0a7e24-45fb-55d8-67f6-377b153810ab@SystematicSw.ab.ca> (raw)
In-Reply-To: <announce.d744b23b-75c7-1ee1-9b94-15736fc47b98@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On 2020-09-18 23:19, JonY via Cygwin-announce wrote:
> Now released for both 32bit and 64bit Cygwin:
>
> w32api-headers-8.0.0-1
> w32api-runtime-8.0.0-1
>
> Based on mingw-w64-v8.0.0.
May be a definition conflict between updated headers rebuilding cygwin both 32
and 64 before and just after latest updates: see attached log.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
[-- Attachment #2: PVOID_definition_conflict.log --]
[-- Type: text/plain, Size: 1345 bytes --]
c++wrap -fno-exceptions -fno-rtti -Wimplicit-fallthrough=4 -Werror -O2 -g -fno-threadsafe-statics -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -c -o cygpath.o ../../.././winsup/utils/cygpath.cc
../../.././winsup/utils/cygpath.cc:27:33: error: conflicting declaration 'typedef struct MEM_EXTENDED_PARAMETER* PVOID'
27 | #define PMEM_EXTENDED_PARAMETER PVOID
| ^~~~~
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/utils/cygpath.cc:28:
/usr/include/w32api/winnt.h:257:17: note: previous declaration as 'typedef void* PVOID'
257 | typedef void *PVOID;
| ^~~~~
make[3]: *** [../../.././winsup/utils/../Makefile.common:41: cygpath.o] Error 1
make[3]: Leaving directory '.../newlib-cygwin/x86_64-pc-cygwin/winsup/utils'
/bin/sh: 1: [: utils: unexpected operator
make[2]: *** [Makefile:81: utils] Error 2
make[2]: Leaving directory '.../newlib-cygwin/x86_64-pc-cygwin/winsup'
make[1]: *** [Makefile:9464: all-target-winsup] Error 2
make[1]: Leaving directory '.../newlib-cygwin'
make: *** [Makefile:883: all] Error 2
next prev parent reply other threads:[~2020-09-22 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 5:19 [ANNOUNCEMENT] Updated: w32api-{headers, runtime}-8.0.0-1 (x86/x86_64) JonY via Cygwin-announce
2020-09-22 22:10 ` Brian Inglis [this message]
2020-09-23 4:17 ` Updated: w32api-{headers,runtime}-8.0.0-1 (x86/x86_64) Brian Inglis
2020-09-23 4:44 ` Brian Inglis
2020-09-23 14:49 ` Ken Brown
2020-09-23 15:21 ` Brian Inglis
2020-09-23 23:57 ` Ken Brown
2020-09-24 16:22 ` Brian Inglis
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=9a0a7e24-45fb-55d8-67f6-377b153810ab@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).