From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gdb: Upgrade 17.2 -> 18.1
Date: Tue, 29 Sep 2026 17:49:45 +0100 [thread overview]
Message-ID: <ead8d2cc390637ec9ea43c4561e4647f4be9d479.camel@linuxfoundation.org> (raw)
In-Reply-To: <18D9D86F8320E53B.2723932@lists.openembedded.org>
On Tue, 2026-09-29 at 17:44 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Tue, 2026-09-29 at 17:56 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> >
> > On 2026-09-29 14:08, Richard Purdie wrote:
> > > On Tue, 2026-09-29 at 11:35 +0200, Jaipaul Cheernam via
> > > lists.openembedded.org wrote:
> > > > NEWS:
> > > > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-18.1-release
> > > >
> > > > - Refresh existing patches
> > > >
> > > > Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> > > I think this triggered:
> > >
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/4785
> > >
> > Hi Richard,
> >
> > I tried different combinations(with musl and without) locally on my
> > machine (ubuntu 24) and no issues found.
> >
> > Could this is be host contamination or sstate issue ?
> >
> > Can you retrigger autobuilder again ?
>
> No, I'm not doing that. A better question is could we look at
> config.log from the failing build. We can and it says:
>
> configure:29766: gcc -o conftest -isystem/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/usr/include -O2 -pipe -isystem/srv/pokybuil
> d/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/usr/include -I/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-
> x86_64/18.1/recipe-sysroot-native/usr/include -L/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/usr/lib -L/srv/p
> okybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/srv
> /pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/srv/pokybuild/yocto-worker/musl-qemux86-64/b
> uild/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/lib -Wl,-rpath,/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/
> 18.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86_64-linux/gdb-cross-x86_64/18.1/recipe-sysroot-native/lib
> -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread conftest.c -lncurse
> sw -latomic -lm >&5
> configure:29766: $? = 0
> configure:29766: ./conftest
> ./conftest: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
> configure:29766: $? = 127
>
> which gives at least some hint as to what the issue may be...
https://valkyrie.yocto.io/pub/shared-failure-data/config.log-gdb
Cheers,
Richard
next prev parent reply other threads:[~2026-09-29 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 9:35 [PATCH] gdb: Upgrade 17.2 -> 18.1 Jaipaul Cheernam
2026-09-29 12:08 ` [OE-core] " Richard Purdie
2026-09-29 15:56 ` Jaipaul Cheernam
2026-09-29 16:44 ` Richard Purdie
2026-09-29 17:10 ` Khem Raj
[not found] ` <18D9D86F8320E53B.2723932@lists.openembedded.org>
2026-09-29 16:49 ` Richard Purdie [this message]
2026-09-30 7:17 ` [PATCH v2] " Jaipaul Cheernam
2026-10-05 19:19 ` Jaipaul Cheernam
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=ead8d2cc390637ec9ea43c4561e4647f4be9d479.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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