public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Cl?ment Chigot <helflym@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5042] configure: remove dependencies on gmp and mpfr when gdb is disabled Date: Fri, 6 Jan 2023 09:03:35 +0000 (GMT) [thread overview] Message-ID: <20230106090335.DB45F3858D33@sourceware.org> (raw) https://gcc.gnu.org/g:5977d14a6081184ba10a671585e553e1e9ac0112 commit r13-5042-g5977d14a6081184ba10a671585e553e1e9ac0112 Author: Clément Chigot <chigot@adacore.com> Date: Tue Jan 3 14:24:43 2023 +0100 configure: remove dependencies on gmp and mpfr when gdb is disabled Since 91e0d22025e0bf2af2e364cb7214a05512a0c431, the configure checks about GMP and MPFR for gdb builds have been moved to the toplevel configure. However, it doesn't take into account the --disable-gdb option. Meaning that a build without gdb will require these libraries even if not needed. ChangeLog: * configure.ac: Skip GMP and MPFR when --disable-gdb is provided. * configure: Regenerate. Diff: --- configure | 4 +++- configure.ac | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/configure b/configure index d6716e38e99..85883099410 100755 --- a/configure +++ b/configure @@ -7913,7 +7913,9 @@ if test -d ${srcdir}/gcc ; then require_mpc=yes fi if test -d ${srcdir}/gdb ; then - require_gmp=yes + if test "x$enable_gdb" != xno; then + require_gmp=yes + fi fi gmplibs="-lmpfr -lgmp" diff --git a/configure.ac b/configure.ac index 737c1a1172b..2b612dce6e9 100644 --- a/configure.ac +++ b/configure.ac @@ -1489,7 +1489,9 @@ if test -d ${srcdir}/gcc ; then require_mpc=yes fi if test -d ${srcdir}/gdb ; then - require_gmp=yes + if test "x$enable_gdb" != xno; then + require_gmp=yes + fi fi gmplibs="-lmpfr -lgmp"
reply other threads:[~2023-01-06 9:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230106090335.DB45F3858D33@sourceware.org \ --to=helflym@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).