Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] recipes: Drop ld-is-gold support
Date: Fri, 07 Feb 2025 16:09:28 +0000	[thread overview]
Message-ID: <96fbc2c08d23e3485497e3b7cc9ba235c2a9176d.camel@linuxfoundation.org> (raw)
In-Reply-To: <D7MCDFANDYTT.2NNXQR99MAHC7@bootlin.com>

On Fri, 2025-02-07 at 17:08 +0100, Mathieu Dubois-Briand wrote:
> On Thu Feb 6, 2025 at 3:49 PM CET, Richard Purdie via
> lists.openembedded.org wrote:
> > Gold hasn't seen development in some time and is being dropped from
> > binutils
> > releases. Drop the small number of special cases for it we were
> > carrying.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> 
> Hi Richard,
> 
> We get some errors while building go. I fear this comes from this
> patch:
> 
> > # /srv/pokybuild/yocto-worker/genericarm64-
> > alt/build/build/tmp/work/armv8a-poky-linux/go-
> > runtime/1.22.11/build-tmp/go-build691092281/b285/libstd.so
> > /srv/pokybuild/yocto-worker/genericarm64-
> > alt/build/build/tmp/work/armv8a-poky-linux/go-
> > runtime/1.22.11/go/pkg/tool/native_native/link: running aarch64-
> > poky-linux-gcc failed: exit status 1
> > collect2: fatal error: cannot find 'ld'
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/974/steps/11/logs/stdio

I'm seeing them too and fear you may be right. It is only on aarch64 :/

Cheers,

Richard


      reply	other threads:[~2025-02-07 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 14:49 [PATCH] recipes: Drop ld-is-gold support Richard Purdie
2025-02-06 16:05 ` [OE-core] " Khem Raj
2025-02-07 16:08 ` Mathieu Dubois-Briand
2025-02-07 16:09   ` Richard Purdie [this message]

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=96fbc2c08d23e3485497e3b7cc9ba235c2a9176d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mathieu.dubois-briand@bootlin.com \
    --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