From: Nick Clifton <nickc@redhat.com>
To: "Clément Chigot" <chigot@adacore.com>,
"Andrew Pinski" <pinskia@gmail.com>
Cc: binutils@sourceware.org, apinski@marvell.com,
Jeff Law <jeffreyalaw@gmail.com>, Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCHv2] Use toplevel configure for GMP and MPFR for gdb
Date: Tue, 3 Jan 2023 11:51:56 +0000 [thread overview]
Message-ID: <bf357369-c051-4250-b85e-32efd3e133c7@redhat.com> (raw)
In-Reply-To: <CAJ307EhzqtqKip56jX7HPXQKTALHe+2STrNb_03MysRZHdOc+w@mail.gmail.com>
Hi Clément,
> Since this patch, binutils without mpfr and gmp is unable to build
> when gdb is disabled (with configure option --disable-gdb). But
> AFAICT, these libraries are not required if gdb isn't there.
Agreed - binutils does not use them.
> Moreover, the following error looks wrong to me when gdb is explicitly
> requested not to be built.
> | configure: error: Building GDB requires GMP 4.2+, and MPFR 3.1.0+.
> | Try the --with-gmp and/or --with-mpfr options to specify
Yup - the message should not be generated if gdb is not being built.
> Thus, I'm wondering if there are any plans to also use gmp and mpfr in
> binutils without gdb (adding Nick for that) ?
No - there are none.
> Or is this patch only meant for gdb and should be adjusted for --disable-gdb ?
It should be adjusted.
Cheers
Nick
next prev parent reply other threads:[~2023-01-03 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:05 apinski
2022-11-16 3:59 ` Jeff Law
2022-11-16 16:01 ` Tom Tromey
2022-11-16 18:50 ` Jeff Law
2022-12-20 18:59 ` Tom Tromey
2022-12-21 3:45 ` Andrew Pinski
2022-12-21 14:56 ` Jeff Law
2022-12-21 15:03 ` Tom Tromey
2023-01-03 10:52 ` Clément Chigot
2023-01-03 11:51 ` Nick Clifton [this message]
2023-01-03 11:52 ` Andrew Pinski
2023-01-03 13:12 ` Clément Chigot
2023-08-10 12:47 ` Matthias Klose
2023-08-10 19:00 ` Arsen Arsenović
-- strict thread matches above, loose matches on Subject: below --
2022-11-10 19:03 apinski
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=bf357369-c051-4250-b85e-32efd3e133c7@redhat.com \
--to=nickc@redhat.com \
--cc=apinski@marvell.com \
--cc=binutils@sourceware.org \
--cc=chigot@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jeffreyalaw@gmail.com \
--cc=pinskia@gmail.com \
--cc=tom@tromey.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).