public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Clément Chigot" <chigot@adacore.com>
To: 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,  Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCHv2] Use toplevel configure for GMP and MPFR for gdb
Date: Tue, 3 Jan 2023 14:12:11 +0100	[thread overview]
Message-ID: <CAJ307EgpPnRjzDKgmYU1DzLPkv9-sG4e+izNmwvksv84Yet=Ew@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1n2szX8-CqHpMxv8AOvLvJS7Mjen7KqAKByBnz091SUfg@mail.gmail.com>

Hi Andrew,

On Tue, Jan 3, 2023 at 12:52 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Tue, Jan 3, 2023 at 2:52 AM Clément Chigot <chigot@adacore.com> wrote:
> >
> > Hi guys,
> >
> > Since this patch, binutils without mpfr and gmp is unable to build
> > when gdb is disabled (with configure option --disable-gdb).
>
> The issue only happens if you are building from git repo. the release
> versions of binutils does NOT include the gdb directory so it does not
> matter.

This is the toplevel configure raising an error. The fact that the gdb
directory is embedded or not in the release doesn't matter here.
Moreover, we still want to be able to build from the git repository
with --disable-gdb.

Anyway, Nick answers confirm my idea. The toplevel configure should be
adjusted for --disable-gdb.
I'll take care of that.

Thanks,
Clément

  reply	other threads:[~2023-01-03 13:12 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
2023-01-03 11:52         ` Andrew Pinski
2023-01-03 13:12           ` Clément Chigot [this message]
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='CAJ307EgpPnRjzDKgmYU1DzLPkv9-sG4e+izNmwvksv84Yet=Ew@mail.gmail.com' \
    --to=chigot@adacore.com \
    --cc=apinski@marvell.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=nickc@redhat.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).