From: Thiago Jung Bauermann via Gdb <gdb@sourceware.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 17 build failure with musl
Date: Tue, 03 Feb 2026 03:10:32 +0000 [thread overview]
Message-ID: <87o6m6jzdj.fsf@linaro.org> (raw)
In-Reply-To: <CAFOYHZA-bwse4AOdr69Er7DUVsLuOrQ01ninMFGx5iLLDgCcfA@mail.gmail.com> (Chris Packham via Gdb's message of "Mon, 26 Jan 2026 19:29:21 +1300")
Hello Chris,
Chris Packham via Gdb <gdb@sourceware.org> writes:
> I've just updated crosstool-ng to include gdb 17.1 and the aarch64
> musl toolchain fails with
>
> [ERROR]
> /home/runner/work/crosstool-ng/crosstool-ng/.build/aarch64-unknown-linux-musl/src/gdb/gdbserver/../gdb/arch/aarch64-gcs-linux.h:35:8:
> error: redefinition of 'struct user_gcs'
> [ALL ] 35 | struct user_gcs
> [ALL ] | ^~~~~~~~
> [ALL ] In file included from
> /home/runner/work/crosstool-ng/crosstool-ng/.build/aarch64-unknown-linux-musl/src/gdb/gdbserver/linux-aarch64-low.cc:35:
> [ALL ]
> /home/runner/work/crosstool-ng/crosstool-ng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/ptrace.h:329:8:
> note: previous definition of 'struct user_gcs'
> [ALL ] 329 | struct user_gcs {
> [ALL ] | ^~~~~~~~
>
> Does this ring any bells for anyone? Builds with gdb 16.3 are fine.
Sorry for the delay in responding.
Do you have reproduction instructions for this problem? I'd like to
experiment a bit and see if I can come up with a solution.
--
Thiago
next prev parent reply other threads:[~2026-02-03 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 6:29 Chris Packham via Gdb
2026-01-26 6:55 ` Andrew Pinski via Gdb
2026-01-26 7:31 ` Chris Packham via Gdb
2026-02-03 3:10 ` Thiago Jung Bauermann via Gdb [this message]
2026-02-03 21:56 ` Chris Packham via Gdb
2026-02-04 4:11 ` Thiago Jung Bauermann via Gdb
2026-02-05 0:35 ` Chris Packham via Gdb
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=87o6m6jzdj.fsf@linaro.org \
--to=gdb@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=thiago.bauermann@linaro.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