public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: apinski@marvell.com, gdb-patches@sourceware.org,
	binutils@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCHv2] Use toplevel configure for GMP and MPFR for gdb
Date: Tue, 15 Nov 2022 20:59:07 -0700	[thread overview]
Message-ID: <36e23439-0429-0c02-1998-0b7a025fa64c@gmail.com> (raw)
In-Reply-To: <1668107159-16961-1-git-send-email-apinski@marvell.com>


On 11/10/22 12:05, apinski--- via Gcc-patches wrote:
> From: Andrew Pinski <apinski@marvell.com>
>
> 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.

If the GDB folks confirm they want this behavior, then the toplevel bits 
are fine.

Jeff



  reply	other threads:[~2022-11-16  3:59 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 [this message]
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
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=36e23439-0429-0c02-1998-0b7a025fa64c@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=apinski@marvell.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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).