public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27657] GDB fails to link on MSYS2 and mingw64 looking for BCryptGenRandom
Date: Mon, 29 Mar 2021 15:53:17 +0000 [thread overview]
Message-ID: <bug-27657-4717-IDTjSx760w@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27657-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27657
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I don't know the answer to this, but I'd suggest looking to see if
there are any reports of this problem to gnulib.
gdb doesn't actually use bcrypt.h at all, this is just pulled in
via gnulib for its getrandom module, AFAICT.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-29 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 6:06 [Bug build/27657] New: " chrisj at rtems dot org
2021-03-29 4:29 ` [Bug build/27657] " chrisj at rtems dot org
2021-03-29 15:53 ` tromey at sourceware dot org [this message]
2021-03-29 20:10 ` cbiesinger at google dot com
2021-03-29 20:41 ` chrisj at rtems dot org
2021-03-29 20:46 ` chrisj at rtems dot org
2021-03-29 23:29 ` cbiesinger at google dot com
2021-03-30 15:58 ` ssbssa at sourceware dot org
2021-08-26 10:38 ` ilg at livius dot net
2021-09-03 15:04 ` ovilewade9 at gmail dot com
2022-02-27 23:31 ` tromey at sourceware dot org
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=bug-27657-4717-IDTjSx760w@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).