From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Updated: w32api-{headers,runtime}-8.0.0-1 (x86/x86_64)
Date: Wed, 23 Sep 2020 10:49:40 -0400 [thread overview]
Message-ID: <6ac829c6-5281-ce39-d22b-d57b7d476c1c@cornell.edu> (raw)
In-Reply-To: <0c884817-574a-e171-9bb5-b8d313a5f6ee@SystematicSw.ab.ca>
On 9/23/2020 12:44 AM, Brian Inglis wrote:
> On 2020-09-22 22:17, Brian Inglis wrote:
>> On 2020-09-22 16:10, Brian Inglis wrote:
>>> 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.
>>
>> Sorry, ambigous - to clarify: may be a definition conflict between updated
>> headers rebuilding cygwin both 32 and 64 just after latest updates: see attached log.
>> Cygwin both 32 and 64 builds worked without any problems just before the latest
>> updates.
>
> Tad confusing log messages, but it appears the actual issue may not be a
> conflict to do with PVOID, but with PMEM_EXTENDED_PARAMETER between the below:
>
> $ fgrep -wB12 PMEM_EXTENDED_PARAMETER /usr/include/w32api/winnt.h
> typedef struct DECLSPEC_ALIGN(8) MEM_EXTENDED_PARAMETER {
> __C89_NAMELESS struct {
> DWORD64 Type : MEM_EXTENDED_PARAMETER_TYPE_BITS;
> DWORD64 Reserved : 64 - MEM_EXTENDED_PARAMETER_TYPE_BITS;
> };
> __C89_NAMELESS union {
> DWORD64 ULong64;
> PVOID Pointer;
> SIZE_T Size;
> HANDLE Handle;
> DWORD ULong;
> };
> } MEM_EXTENDED_PARAMETER, *PMEM_EXTENDED_PARAMETER;
> $ fgrep -wA8 PMEM_EXTENDED_PARAMETER winsup/utils/cygpath.cc
> #define PMEM_EXTENDED_PARAMETER PVOID
> #include <windows.h>
> #include <userenv.h>
> #include <shlobj.h>
> #include <ntdef.h>
> #include <ntdll.h>
>
> #include "wide_path.h"
> #include "loadlib.h"
>
> It seems likely that we could perhaps just remove the conflicting #define, but
> without some idea of the original intent and its impact, and a good cygpath
> regression test suite, that could perhaps be a rash decision.
This is related to the extended memory API that Corinna started using last
April. At the time the relevant declarations and definitions weren't in the
mingw-w64 headers yet, so Corinna had to do some ad hoc stuff. Now that they've
been added, a lot of that stuff should be removed. I'll do it later today.
Ken
next prev parent reply other threads:[~2020-09-23 14:49 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 ` Updated: w32api-{headers,runtime}-8.0.0-1 (x86/x86_64) Brian Inglis
2020-09-23 4:17 ` Brian Inglis
2020-09-23 4:44 ` Brian Inglis
2020-09-23 14:49 ` Ken Brown [this message]
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=6ac829c6-5281-ce39-d22b-d57b7d476c1c@cornell.edu \
--to=kbrown@cornell.edu \
--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).