From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] gdb: add option for 11.1 and later
Date: Fri, 11 Nov 2022 15:31:22 +0100 [thread overview]
Message-ID: <20221111143122.894228-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221103165542.469895-1-p.zabel@pengutronix.de>
Thanks, applied as 09e0190646c7f46c15c8e084dd6810c1246db46e.
Michael
[sent from post-receive hook]
On Fri, 11 Nov 2022 15:31:22 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> GDB requires GMP since version 11.1. Add an option to allow selecting
> LIBGMP for newer toolchains. This is somewhat analogous to commit
> bc5cac5c54d2 ("glibc: add option for 2.34 and later").
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20221103165542.469895-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gdb.in b/rules/gdb.in
> index 1dd2213abc8a..3014271de9c1 100644
> --- a/rules/gdb.in
> +++ b/rules/gdb.in
> @@ -7,6 +7,7 @@ menuconfig GDB
> select LIBC_DL
> select GCCLIBS_GCC_S
> select NCURSES
> + select LIBGMP if GDB_11_1
> help
> The GNU Debugger
>
> @@ -25,5 +26,12 @@ config GDB_SHARED
> If not set, the build option
> LDFLAGS=-static will be activated.
>
> +config GDB_11_1
> + bool
> + prompt "gdb-11.1 or later"
> + help
> + Since gdb-11.1, GMP is a required dependency. Enable this option
> + if your toolchain gdb version is 11.1 or later.
> +
> endif
>
prev parent reply other threads:[~2022-11-11 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:55 [ptxdist] [PATCH] " Philipp Zabel
2022-11-04 8:12 ` Ladislav Michl
2022-11-11 14:31 ` Michael Olbrich [this message]
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=20221111143122.894228-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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