mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] gdb: add option for 11.1 and later
Date: Fri, 4 Nov 2022 09:12:06 +0100	[thread overview]
Message-ID: <Y2TJVqFQVqtGciFY@lenoch> (raw)
In-Reply-To: <20221103165542.469895-1-p.zabel@pengutronix.de>

Hi Philipp!

On Thu, Nov 03, 2022 at 05:55:42PM +0100, Philipp Zabel 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").

before adding one more analogous commit, what about turning both of
them to something like
	def_bool $(success,test "you_test_goes_there")


> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
>  rules/gdb.in | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> 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
>  
> -- 
> 2.30.2
> 



  reply	other threads:[~2022-11-04  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 16:55 Philipp Zabel
2022-11-04  8:12 ` Ladislav Michl [this message]
2022-11-11 14:31 ` [ptxdist] [APPLIED] " Michael Olbrich

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=Y2TJVqFQVqtGciFY@lenoch \
    --to=oss-lists@triops.cz \
    --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