Bug 29933 - [Regression] Toplevel configure does not honor --disable-gdb for GMP/MPFR check
Summary: [Regression] Toplevel configure does not honor --disable-gdb for GMP/MPFR check
Status: RESOLVED FIXED
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: 14.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-22 10:29 UTC by Pekka Seppänen
Modified: 2024-01-06 15:26 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pekka Seppänen 2022-12-22 10:29:23 UTC 
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.
Comment 1 Robin Lee 2023-02-07 01:53:30 UTC 
I met the same issue and work it around by removing the gdb directory.