public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pexu at sourceware dot mail.kapsi.fi" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29933] New: [Regression] Toplevel configure does not honor --disable-gdb for GMP/MPFR check
Date: Thu, 22 Dec 2022 10:29:23 +0000	[thread overview]
Message-ID: <bug-29933-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29933

            Bug ID: 29933
           Summary: [Regression] Toplevel configure does not honor
                    --disable-gdb for GMP/MPFR check
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: pexu at sourceware dot mail.kapsi.fi
  Target Milestone: ---

Hi.

As of 991180627851801f1999d1ebbc0e569a17e47c74 GMP and MPFR configuration is
now moved to toplevel configure.

However, if gdb is disabled with --disable-gdb the toplevel configure still
applies require_gmp=yes if the source directory ${srcdir}/gdb exists.  However,
this check should honor --disable-gdb (i.e. noconfigdirs) and not only test for
the source directory existence.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-12-22 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 10:29 pexu at sourceware dot mail.kapsi.fi [this message]
2023-02-07  1:53 ` [Bug gdb/29933] " robinlee.sysu at gmail dot com
2024-01-06 15:26 ` ssbssa at sourceware dot org

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=bug-29933-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).