From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] gdb: Version bump. 11.1 -> 11.2
Date: Mon, 14 Feb 2022 13:43:42 +0100 [thread overview]
Message-ID: <20220214124342.840027-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220207191956.228076-1-christian.melki@t2data.com>
Thanks, applied as 438d36c6edfb0a05833a961566d4d54fbd85e14f.
Michael
[sent from post-receive hook]
On Mon, 14 Feb 2022 13:43:41 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> https://www.sourceware.org/gdb/download/ANNOUNCEMENT
> Bump default version.
> A lot of problems with aarch64 and 11.1 was due to pr28355.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220207191956.228076-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gdb-menu.in b/rules/gdb-menu.in
> index 74ede3085c9c..00c7ef436a79 100644
> --- a/rules/gdb-menu.in
> +++ b/rules/gdb-menu.in
> @@ -18,12 +18,12 @@ if !GDB_TOOLCHAIN_VERSION
>
> config GDB_VERSION
> string "gdb version"
> - default "11.1"
> + default "11.2"
> endif
>
> config GDB_MD5
> string "gdb source md5sum"
> - default "257cb0f67927f79acf636d8c01e19990" if !GDB_TOOLCHAIN_VERSION
> + default "433bd0904caa31c247b1b1867f2f911d" if !GDB_TOOLCHAIN_VERSION
> help
> md5sum for the gdb source archive. If the version is provided by
> the toolchain and the toolchain is an OSELAS.Toolchain then this
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2022-02-14 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 19:19 [ptxdist] [PATCH] " Christian Melki
2022-02-14 12:43 ` 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=20220214124342.840027-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--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