From: Jeff Law <jeffreyalaw@gmail.com>
To: Tom Tromey <tom@tromey.com>,
Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: apinski@marvell.com, gdb-patches@sourceware.org,
binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCHv2] Use toplevel configure for GMP and MPFR for gdb
Date: Wed, 16 Nov 2022 11:50:20 -0700 [thread overview]
Message-ID: <2323eb79-6be5-4661-59b8-fb30fb2fb743@gmail.com> (raw)
In-Reply-To: <87edu2vqfv.fsf@tromey.com>
On 11/16/22 09:01, Tom Tromey wrote:
>>>>>> "Jeff" == Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>>> This patch uses the toplevel configure parts for GMP/MPFR for
>>> gdb.
> Jeff> If the GDB folks confirm they want this behavior, then the toplevel
> Jeff> bits are fine.
>
> I think we do, but my inclination is to wait until after GDB 13 branches.
> CCing Joel to see what he thinks, as he handles the releases.
I think I may have cut too much context. At some point I know I saw a
note that it wouldn't be installed until after gdb-13 releases/branches.
jeff
next prev parent reply other threads:[~2022-11-16 18:50 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 [this message]
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
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=2323eb79-6be5-4661-59b8-fb30fb2fb743@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=apinski@marvell.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--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).