From: Christian Biesinger <cbiesinger@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: simon.cook@embecosm.com, Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Unable to build GDB on Windows
Date: Mon, 28 Sep 2020 17:17:49 +0200 [thread overview]
Message-ID: <CAPTJ0XGEpMN=JWDYmEZ6KAj3Ucbfpz7SJsApML61uE_Jfjcm1g@mail.gmail.com> (raw)
In-Reply-To: <83zh5aklls.fsf@gnu.org>
On Mon, Sep 28, 2020 at 4:44 PM Eli Zaretskii via Gdb
<gdb@sourceware.org> wrote:
> Btw, looking at Gnulib's getrandom.c, my conclusion is that a GDB
> built on Windows 7 and later will be unable to run on older versions
> of Windows, because it will have a static dependency on bcrypt.dll and
> the BCryptGenRandom function from that DLL. IOW, such a GDB will
> refuse to run on older Windows systems.
>
> OTOH, if you build on Windows before 7, the produced binary will be
> able to run on newer versions of Windows by dynamically loading
> bcrypt.dll (when available) at run time, and using a fallback
> otherwise.
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)
Christian
next prev parent reply other threads:[~2020-09-28 15:18 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 [this message]
2020-09-28 15:23 ` Eli Zaretskii
2020-09-28 15:29 ` Eli Zaretskii
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='CAPTJ0XGEpMN=JWDYmEZ6KAj3Ucbfpz7SJsApML61uE_Jfjcm1g@mail.gmail.com' \
--to=cbiesinger@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=simon.cook@embecosm.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).