From: Eli Zaretskii <eliz@gnu.org>
To: Simon Cook <simon.cook@embecosm.com>
Cc: gdb@sourceware.org
Subject: Re: Unable to build GDB on Windows
Date: Mon, 28 Sep 2020 17:25:25 +0300 [thread overview]
Message-ID: <833632m10q.fsf@gnu.org> (raw)
In-Reply-To: <CAFOzG3sputSOnJCTVG3X0t3Zic6UCnbfSbw_hUppkOT_MQ=bbA@mail.gmail.com> (message from Simon Cook on Mon, 28 Sep 2020 14:47:25 +0100)
> From: Simon Cook <simon.cook@embecosm.com>
> Date: Mon, 28 Sep 2020 14:47:25 +0100
>
> I've been trying to build top of tree GDB on Windows (natively under
> the MSYS2 environment), and haven't been able to link successfully due
> to undefined symbols after linking against gnulib:
>
> CXXLD gdb.exe
> ../gnulib/import/libgnu.a(getrandom.o): In function `getrandom':
> C:\msys64s\home\simon\work\b\gnulib\import/../../../binutils-gdb/gnulib/import/getrandom.c:129:
> undefined reference to `BCryptGenRandom'
> collect2.exe: error: ld returned 1 exit status
>
> Reading through the source file and gnulib/import/m4/getrandom.m4, it
> suggests that in my case if bcrypt can be guaranteed to be present
> then I should add -lbcrypt to my linker flags to resolve these
> references, and indeed if I execute the failing gdb link command and
> add -lbcrypt at the end then my link succeeds.
What version of MS-Windows is that?
What is the value of gl_cv_lib_assume_bcrypt in gnulib/config.cache?
And what do you see in gnulib/config.log about the test
checking whether the bcrypt library is guaranteed to be present
> Is this an issue that anyone has seen before? It's not clear on my
> side whether there's an issue with my environment causing that
> dependency to be needed, and something missing from the GDB makefiles.
Hmm, looks like we are missing LIB_GETRANDOM in gdb/Makefile?
next prev parent reply other threads:[~2020-09-28 14:25 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 [this message]
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
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=833632m10q.fsf@gnu.org \
--to=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).