public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "chrisj at rtems 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 04:29:26 +0000 [thread overview]
Message-ID: <bug-27657-4717-rvLH58DMBi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27657-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27657
--- Comment #1 from Chris Johns <chrisj at rtems dot org> ---
The gnulib config.log has this ...
configure:20640: checking bcrypt.h usability
configure:20640: x86_64-w64-mingw32-gcc -O2 -g -pipe
-I/d/opt/rtems/rsb.git/rtems/build/tmp/sb-197609/6s/d/opt/rtems/6/include -c -g
-O2 -D__USE_MINGW_ACCESS conftest.c >&5
In file included from conftest.c:192:
C:/msys64/mingw64/x86_64-w64-mingw32/include/bcrypt.h:27:11: error: unknown
type name 'LONG'
27 | typedef LONG NTSTATUS,*PNTSTATUS;
| ^~~~
C:/msys64/mingw64/x86_64-w64-mingw32/include/bcrypt.h:174:5: error: unknown
type name 'ULONG'
174 | ULONG dwMinLength;
| ^~~~~
C:/msys64/mingw64/x86_64-w64-mingw32/include/bcrypt.h:175:5: error: unknown
type name 'ULONG'
175 | ULONG dwMaxLength;
| ^~~~~
C:/msys64/mingw64/x86_64-w64-mingw32/include/bcrypt.h:176:5: error: unknown
type name 'ULONG'
176 | ULONG dwIncrement;
| ^~~~~
C:/msys64/mingw64/x86_64-w64-mingw32/include/bcrypt.h:182:5: error: unknown
type name 'ULONG'
Should windows.h or something like that be included?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-29 4:29 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 ` chrisj at rtems dot org [this message]
2021-03-29 15:53 ` [Bug build/27657] " tromey at sourceware dot org
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-rvLH58DMBi@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).