public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/28500] Failure to find libgmp Date: Wed, 21 Dec 2022 16:51:45 +0000 [thread overview] Message-ID: <bug-28500-4717-WTYSEmJ6gv@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28500-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28500 --- Comment #20 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Pinski <pinskia@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=991180627851801f1999d1ebbc0e569a17e47c74 commit 991180627851801f1999d1ebbc0e569a17e47c74 Author: Andrew Pinski <apinski@marvell.com> Date: Tue Nov 8 07:57:18 2022 +0000 Use toplevel configure for GMP and MPFR for gdb This patch uses the toplevel configure parts for GMP/MPFR for gdb. The only thing is that gdb now requires MPFR for building. Before it was a recommended but not required library. Also this allows building of GMP and MPFR with the toplevel directory just like how it is done for GCC. We now error out in the toplevel configure of the version of GMP and MPFR that is wrong. OK after GDB 13 branches? Build gdb 3 ways: with GMP and MPFR in the toplevel (static library used at that point for both) With only MPFR in the toplevel (GMP distro library used and MPFR built from source) With neither GMP and MPFR in the toplevel (distro libraries used) Changes from v1: * Updated gdb/README and gdb/doc/gdb.texinfo. * Regenerated using unmodified autoconf-2.69 Thanks, Andrew Pinski ChangeLog: * Makefile.def: Add configure-gdb dependencies on all-gmp and all-mpfr. * configure.ac: Split out MPC checking from MPFR. Require GMP and MPFR if the gdb directory exist. * Makefile.in: Regenerate. * configure: Regenerate. gdb/ChangeLog: PR bug/28500 * configure.ac: Remove AC_LIB_HAVE_LINKFLAGS for gmp and mpfr. Use GMPLIBS and GMPINC which is provided by the toplevel configure. * Makefile.in (LIBGMP, LIBMPFR): Remove. (GMPLIBS, GMPINC): Add definition. (INTERNAL_CFLAGS_BASE): Add GMPINC. (CLIBS): Exchange LIBMPFR and LIBGMP for GMPLIBS. * target-float.c: Make the code conditional on HAVE_LIBMPFR unconditional. * top.c: Remove code checking HAVE_LIBMPFR. * configure: Regenerate. * config.in: Regenerate. * README: Update GMP/MPFR section of the config options. * doc/gdb.texinfo: Likewise. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28500 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-21 16:51 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 18:34 [Bug build/28500] New: " 64m at tutamail dot com 2021-10-26 18:50 ` [Bug build/28500] " 64m at tutamail dot com 2021-10-26 18:52 ` 64m at tutamail dot com 2022-02-27 20:54 ` tromey at sourceware dot org 2022-03-06 9:55 ` 64m at tutamail dot com 2022-03-06 10:42 ` 64m at tutamail dot com 2022-03-06 10:44 ` 64m at tutamail dot com 2022-03-06 15:52 ` tromey at sourceware dot org 2022-03-06 15:54 ` tromey at sourceware dot org 2022-03-06 16:09 ` tromey at sourceware dot org 2022-03-06 16:09 ` tromey at sourceware dot org 2022-03-06 16:09 ` tromey at sourceware dot org 2022-05-02 20:13 ` karel.gardas at centrum dot cz 2022-07-28 15:40 ` sourceware at boris dot nikolaus.name 2022-07-28 16:02 ` simon.marchi at polymtl dot ca 2022-11-08 2:58 ` pinskia at gcc dot gnu.org 2022-11-08 3:01 ` pinskia at gcc dot gnu.org 2022-11-08 7:26 ` pinskia at gcc dot gnu.org 2022-11-08 8:03 ` pinskia at gcc dot gnu.org 2022-11-08 16:30 ` pinskia at gcc dot gnu.org 2022-12-21 16:51 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-21 16:55 ` pinskia at gcc dot gnu.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-28500-4717-WTYSEmJ6gv@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: 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).