On Tue, Feb 24, 2026 at 03:14 PM, Mathieu Dubois-Briand wrote:

> 
> Hi Sunil,
> 
> Thanks for the new version.
> 
> It looks like we still have a musl issue, but specifically while
> building for qemuarm64 machine:
> 
> ERROR: gdb-17.1-r0 do_compile: Execution of
> '/srv/pokybuild/yocto-worker/musl-qemuarm64/build/build/tmp/work/cortexa57-poky-linux-musl/gdb/17.1/temp/run.do_compile.2065169'
> failed with exit code 1
> ...
> | In file included from
> ../../sources/gdb-17.1/gdbserver/linux-aarch64-low.cc:42:
> | ../../sources/gdb-17.1/gdbserver/../gdb/arch/aarch64-gcs-linux.h:35:8:
> error: redefinition of 'struct user_gcs'
> | 35 | struct user_gcs
> | | ^~~~~~~~
> | In file included from
> ../../sources/gdb-17.1/gdbserver/linux-aarch64-low.cc:35:
> |
> /srv/pokybuild/yocto-worker/musl-qemuarm64/build/build/tmp/work/cortexa57-poky-linux-musl/gdb/17.1/recipe-sysroot/usr/include/asm/ptrace.h:329:8:
> note: previous definition of 'struct user_gcs'
> | 329 | struct user_gcs {
> | | ^~~~~~~~
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/1970
> 
> Can you have a look at it?

Hi Mathieu,

Thanks for the report.

I’ve checked the failure. It’s another musl-specific issue with the new AArch64 
GCS support in GDB 17.1.
struct user_gcs is now provided by musl via <asm/ptrace.h> , while GDB still 
has its own fallback definition
in aarch64-gcs-linux.h , which causes the duplicate definition error.

GDB has guards around the fallback definition, but they don’t work correctly 
with musl’s header layout.
This does not happen with glibc due to different header inclusion behavior.

I’m working on a fix and will send an updated patch shortly.

Thanks,
Sunil

> 
> 
> Thanks,
> Mathieu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#231902): 
https://lists.openembedded.org/g/openembedded-core/message/231902
Mute This Topic: https://lists.openembedded.org/mt/117955476/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to