From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags
Date: Tue, 28 Feb 2023 23:45:04 +0100 [thread overview]
Message-ID: <Y/6D8FQZMWzf4TZq@mail.local> (raw)
In-Reply-To: <e5614f07a3ec48650b1bcea2a3df570e725234d2.camel@linuxfoundation.org>
On 28/02/2023 17:50:05+0000, Richard Purdie wrote:
> On Tue, 2023-02-28 at 08:43 -0800, Khem Raj wrote:
> > On Tue, Feb 28, 2023 at 8:18 AM Alexandre Belloni
> > <alexandre.belloni@bootlin.com> wrote:
> > >
> > > Hello Khem,
> > >
> > > As discussed I gave it a go again and got this:
> > >
> > > > /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: linux-tdep.o: in function `linux_corefile_thread(thread_info*, linux_corefile_thread_data*)':
> > > > linux-tdep.c:(.text+0x13ac): undefined reference to `gcore_elf_build_thread_register_notes(gdbarch*, thread_info*, gdb_signal, bfd*, std::unique_ptr<char, gdb::xfree_deleter<char> >*, int*)'
> > > > /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: linux-tdep.o: in function `linux_make_corefile_notes(gdbarch*, bfd*, int*)':
> > > > linux-tdep.c:(.text+0x49d7): undefined reference to `gcore_elf_make_tdesc_note(bfd*, std::unique_ptr<char, gdb::xfree_deleter<char> >*, int*)'
> > > > collect2: error: ld returned 1 exit status
> > > > make[2]: *** [Makefile:2149: gdb] Error 1
> > > > make[2]: Leaving directory '/home/pokybuild/yocto-worker/qemuarm/build/build/tmp/work/x86_64-linux/gdb-cross-arm/13.1-r0/build-arm-poky-linux-gnueabi/gdb'
> > > > make[1]: *** [Makefile:11122: all-gdb] Error 2
> > > > make[1]: Leaving directory '/home/pokybuild/yocto-worker/qemuarm/build/build/tmp/work/x86_64-linux/gdb-cross-arm/13.1-r0/build-arm-poky-linux-gnueabi'
> > > > make: *** [Makefile:1005: all] Error 2
> > > > ERROR: oe_runmake failed
> >
> > Is this host running updated buildtools tarball after the binutils ld
> > search path fix ?
>
> Yes, it should be.
Khem, you are probably right that this is host related, this failed
again on ubuntu2004:
https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/6689/steps/14/logs/stdio
I'm wondering whether this reproduces on master and we have simply been
lucky.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-02-28 22:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 6:58 [PATCH] binutils: Enable --enable-new-dtags Khem Raj
2023-02-23 23:34 ` [OE-core] " Alexandre Belloni
2023-02-24 1:56 ` Khem Raj
2023-02-27 6:43 ` Khem Raj
2023-02-27 8:37 ` Richard Purdie
2023-02-28 16:18 ` Alexandre Belloni
2023-02-28 16:43 ` Khem Raj
2023-02-28 17:50 ` Richard Purdie
2023-02-28 22:45 ` Alexandre Belloni [this message]
2023-03-01 9:25 ` Alexandre Belloni
[not found] ` <17484164C4F9625C.21178@lists.openembedded.org>
2023-03-02 11:41 ` Alexandre Belloni
2023-03-02 13:18 ` Richard Purdie
[not found] ` <17489CAAF65A13B6.9697@lists.openembedded.org>
2023-03-02 17:54 ` Richard Purdie
[not found] ` <1748ABB9EC6D9FC3.21180@lists.openembedded.org>
2023-03-02 22:47 ` Richard Purdie
2023-03-08 9:33 ` Richard Purdie
[not found] ` <174A67E2AA88DEE8.12537@lists.openembedded.org>
2023-03-08 11:53 ` Richard Purdie
2023-03-08 15:19 ` Khem Raj
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=Y/6D8FQZMWzf4TZq@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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