Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/3] package/gdb: add support for GDB 13.2
Date: Sun, 6 Aug 2023 16:41:55 +0200	[thread overview]
Message-ID: <20230806164155.056a7cd5@windsurf> (raw)
In-Reply-To: <20230802214950.1817381-1-thomas.petazzoni@bootlin.com>

On Wed,  2 Aug 2023 23:49:46 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:

> Sadly, the stack of patches remain exactly the same, none of the
> changes have been upstreamed.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
>  .checkpackageignore                           |  9 +++
>  ...e-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 55 ++++++++++++++++
>  ...-pt_-dsp-regs-uapi_pt_-dsp-regs-on-G.patch | 43 +++++++++++++
>  package/gdb/13.2/0003-use-asm-sgidefs.h.patch | 40 ++++++++++++
>  .../0004-gdbserver-fix-build-for-m68k.patch   | 63 +++++++++++++++++++
>  ...fork-inferior-include-linux-ptrace.h.patch | 53 ++++++++++++++++
>  ...getrandom-compile-for-uclibc-v1.0.35.patch | 39 ++++++++++++
>  .../13.2/0007-fix-musl-build-on-riscv.patch   | 60 ++++++++++++++++++
>  ...-gdbserver-Makefile.in-fix-NLS-build.patch | 38 +++++++++++
>  .../0009-gdb-Fix-native-build-on-xtensa.patch | 57 +++++++++++++++++
>  package/gdb/Config.in.host                    |  4 ++
>  package/gdb/gdb.hash                          |  1 +
>  12 files changed, 462 insertions(+)
>  create mode 100644 package/gdb/13.2/0001-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch
>  create mode 100644 package/gdb/13.2/0002-sh-ptrace-Define-pt_-dsp-regs-uapi_pt_-dsp-regs-on-G.patch
>  create mode 100644 package/gdb/13.2/0003-use-asm-sgidefs.h.patch
>  create mode 100644 package/gdb/13.2/0004-gdbserver-fix-build-for-m68k.patch
>  create mode 100644 package/gdb/13.2/0005-nat-fork-inferior-include-linux-ptrace.h.patch
>  create mode 100644 package/gdb/13.2/0006-Fix-getrandom-compile-for-uclibc-v1.0.35.patch
>  create mode 100644 package/gdb/13.2/0007-fix-musl-build-on-riscv.patch
>  create mode 100644 package/gdb/13.2/0008-gdbserver-Makefile.in-fix-NLS-build.patch
>  create mode 100644 package/gdb/13.2/0009-gdb-Fix-native-build-on-xtensa.patch

Series applied to next. Hopefully I didn't screw up too much.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-08-06 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 21:49 [Buildroot] [PATCH v2 1/3] package/gdb: add support for GDB 13.2 Thomas Petazzoni via buildroot
2023-08-02 21:49 ` [Buildroot] [PATCH v2 2/3] package/gdb: make version 12.x the default Thomas Petazzoni via buildroot
2023-08-02 21:49 ` [Buildroot] [PATCH v2 3/3] package/gdb: remove gdb 10.x Thomas Petazzoni via buildroot
2023-08-06 14:41 ` Thomas Petazzoni via buildroot [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=20230806164155.056a7cd5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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