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 18:14:14 +0300 [thread overview]
Message-ID: <83wo0ekk6x.fsf@gnu.org> (raw)
In-Reply-To: <CAFOzG3uYYP2Vhigz1yMTUFgBq-c4umXdTnCkxbJ8zFUZFy4gLw@mail.gmail.com> (message from Simon Cook on Mon, 28 Sep 2020 16:02:53 +0100)
> From: Simon Cook <simon.cook@embecosm.com>
> Date: Mon, 28 Sep 2020 16:02:53 +0100
> Cc: gdb@sourceware.org
>
> On Mon, Sep 28, 2020 at 3:25 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > What version of MS-Windows is that?
>
> I'm building on 64-bit Windows 10 (version 2004 if that's relevant)
>
> > What is the value of gl_cv_lib_assume_bcrypt in gnulib/config.cache?
>
> gl_cv_lib_assume_bcrypt=${gl_cv_lib_assume_bcrypt=yes}
>
> > And what do you see in gnulib/config.log about the test
> >
> > checking whether the bcrypt library is guaranteed to be present
> >
>
> configure:20630: checking whether the bcrypt library is guaranteed to be present
> configure:20650: gcc -c -g -O2 -D__USE_MINGW_ACCESS conftest.c >&5
> configure:20650: $? = 0
> configure:20658: result: yes
Then I guess the problem is indeed that gdb/Makefile doesn't use
LIB_GETRANDOM, which getrandom.m4 sets as part of the above test.
prev parent reply other threads:[~2020-09-28 15:14 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
2020-09-28 15:02 ` Simon Cook
2020-09-28 15:14 ` Eli Zaretskii [this message]
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=83wo0ekk6x.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).