From: Chris Packham via Gdb <gdb@sourceware.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: GDB Mailing list <gdb@sourceware.org>
Subject: Re: GDB 17 build failure with musl
Date: Mon, 26 Jan 2026 20:31:00 +1300 [thread overview]
Message-ID: <CAFOYHZDDkuaqCtUGY5Q7rBt5qbMK_Kvf2UsajzJAqZ-kVkDzug@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1neuh7tS-+nPq=2uDpwypdBdh38TN3GB9R7wRVECktp1Q@mail.gmail.com>
On Mon, Jan 26, 2026 at 7:55 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Sun, Jan 25, 2026 at 10:30 PM Chris Packham via Gdb
> <gdb@sourceware.org> wrote:
> >
> > Hi GDB,
> >
> > 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.
>
> So aarch64-gcs-linux.h checks to see if GCS_MAGIC is defined to see if
> user_gcs is needed to be declared.
>
> GCS_MAGIC is defined in asm/sigcontext.h while gcs_user is defined in
> asm/ptrace.h.
>
> Maybe the issue is asm/sigcontext.h is not being included (indirectly
> like it is on glibc).
> Try adding
> #include <asm/sigcontext.h>
> After the include of asm/ptrace.h in gdbserver/linux-aarch64-low.cc .
>
Unfortunately that has its own issues
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:28:8:
error: redefinition of 'struct sigcontext'
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:70:8:
error: redefinition of 'struct _aarch64_ctx'
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:77:8:
error: redefinition of 'struct fpsimd_context'
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:96:8:
error: redefinition of 'struct esr_context'
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:136:8:
error: redefinition of 'struct extra_context'
[ERROR] /home/ctng/x-tools/aarch64-unknown-linux-musl/aarch64-unknown-linux-musl/sysroot/usr/include/asm/sigcontext.h:145:8:
error: redefinition of 'struct sve_context'
> Thanks,
> Andrew Pinski
>
>
> >
> > Thanks,
> > Chris
next prev parent reply other threads:[~2026-01-26 7:31 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 [this message]
2026-02-03 3:10 ` Thiago Jung Bauermann via Gdb
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=CAFOYHZDDkuaqCtUGY5Q7rBt5qbMK_Kvf2UsajzJAqZ-kVkDzug@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=pinskia@gmail.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