From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Define PSAPI_VERSION as 1 before including psapi.h
Date: Tue, 6 Jul 2021 15:55:44 +0200 [thread overview]
Message-ID: <YORg4JXAKu4guliV@calimero.vinschen.de> (raw)
In-Reply-To: <20210620133727.63966-1-jon.turney@dronecode.org.uk>
Hi Jon,
On Jun 20 14:37, Jon Turney wrote:
> The default PSAPI_VERSION is controlled by WIN32_WINNT, which we set to
> 0x0a00 when building utils since 48a76190 (and is the default in w32api
> >= 9.0.0)
>
> In order for the built executables to run on Windows Vista, we must also
> define PSAPI_VERSION as 1 (otherwise '#define GetModuleFileNameExA
> K32GetModuleFileNameExA' causes a 'The procedure entry point
> K32GetModuleFilenameExA could not be located in the dynamic link library
> kernel32.dll' error at run time).
>
> Also drop uneeded psapi.h from dlfcn.cc (31ddf45d), resource.cc
> (34a6eeab) and ps.cc (1def2148).
> ---
> winsup/cygwin/dlfcn.cc | 1 -
> winsup/cygwin/resource.cc | 1 -
> winsup/utils/dumper.cc | 1 +
> winsup/utils/ldd.cc | 2 +-
> winsup/utils/mingw/bloda.cc | 1 +
> winsup/utils/module_info.cc | 1 +
> winsup/utils/pldd.c | 1 +
> winsup/utils/ps.cc | 1 -
> 8 files changed, 5 insertions(+), 4 deletions(-)
+1. You really don't have to wait for me to push stuff like that.
Thanks,
Corinna
prev parent reply other threads:[~2021-07-06 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 17:46 [PATCH] Ensure PSAPI_VERSION is 1 when building ldd Jon Turney
2021-05-20 18:05 ` Corinna Vinschen
2021-05-22 15:08 ` Jon Turney
2021-05-25 21:37 ` Jon Turney
2021-05-26 9:04 ` Corinna Vinschen
2021-05-26 16:51 ` Jon Turney
2021-05-26 17:04 ` Yaakov Selkowitz
2021-05-26 19:18 ` Corinna Vinschen
2021-05-27 17:30 ` Jon Turney
2021-05-27 19:08 ` Corinna Vinschen
2021-05-28 15:13 ` Jon Turney
2021-06-20 13:37 ` [PATCH] Define PSAPI_VERSION as 1 before including psapi.h Jon Turney
2021-07-06 13:55 ` Corinna Vinschen [this message]
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=YORg4JXAKu4guliV@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).