From: Eli Zaretskii <eliz@gnu.org>
To: cbiesinger@google.com
Cc: gdb@sourceware.org
Subject: Re: Unable to build GDB on Windows
Date: Mon, 28 Sep 2020 18:29:01 +0300 [thread overview]
Message-ID: <83r1qlly2q.fsf@gnu.org> (raw)
In-Reply-To: <83sgb2kjr8.fsf@gnu.org> (message from Eli Zaretskii via Gdb on Mon, 28 Sep 2020 18:23:39 +0300)
> Date: Mon, 28 Sep 2020 18:23:39 +0300
> From: Eli Zaretskii via Gdb <gdb@sourceware.org>
> Cc: gdb@sourceware.org
>
> > From: Christian Biesinger <cbiesinger@google.com>
> > Date: Mon, 28 Sep 2020 17:17:49 +0200
> > Cc: simon.cook@embecosm.com, Reuben Thomas via Gdb <gdb@sourceware.org>
> >
> > Hmm that sounds odd, usually the way the Windows SDK works is that
> > this only depends on what you #define, not what you build on
> > (especially _WIN32_WINNT)
>
> Well, that's true, but how many will use "CPPFLAGS=-D_WIN32_WINNT=..."
> when configuring GDB? The default is buried somewhere in the MinGW
> headers, and guess what it is?
And actually, in this case the above is not relevant. Because
getrandom.c bases its logic on the configure-time test that results in
HAVE_LIB_BCRYPT defined to either 1 or zero. It doesn't look at
_WIN32_WINNT at all. So yes, the result depends on whether you build
GDB on a system with or without bcrypt.dll.
next prev parent reply other threads:[~2020-09-28 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 13:47 Simon Cook
2020-09-28 14:25 ` Eli Zaretskii
2020-09-28 14:43 ` Eli Zaretskii
2020-09-28 15:15 ` Joel Brobecker
2020-09-28 15:21 ` Eli Zaretskii
2020-09-28 15:17 ` Christian Biesinger
2020-09-28 15:23 ` Eli Zaretskii
2020-09-28 15:29 ` Eli Zaretskii [this message]
2020-09-28 15:02 ` Simon Cook
2020-09-28 15:14 ` Eli Zaretskii
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=83r1qlly2q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
/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).