Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/3] classes/toolchain/clang: compiler-rt and libcxx are not target-specific
Date: Tue, 29 Jul 2025 10:20:29 +0200	[thread overview]
Message-ID: <DBOE54WLIIIG.3RM6KQUS65VQ@bootlin.com> (raw)
In-Reply-To: <20250728155554.2624191-1-ross.burton@arm.com>

On Mon Jul 28, 2025 at 5:55 PM CEST, Ross Burton via lists.openembedded.org wrote:
> This file can be used for nativesdk builds, which if they are using the
> clang toolchain will also need compiler-rt and libcxx.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---

Hi Ross,

It looks like this is breaking something:

ERROR: libcxx-20.1.8-r0 do_package: Error executing a python function in exec_func_python() autogenerated:
...
Exception: FileNotFoundError: [Errno 2] No such file or directory: 'x86_64-poky-linux-musl-objdump'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/2166
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/1957

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      parent reply	other threads:[~2025-07-29  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 15:55 [PATCH 1/3] classes/toolchain/clang: compiler-rt and libcxx are not target-specific Ross Burton
2025-07-28 15:55 ` [PATCH 2/3] clang-cross: trim the recipe Ross Burton
2025-07-28 16:16   ` Patchtest results for " patchtest
2025-07-28 15:55 ` [PATCH 3/3] clang: split lld into a separate lld recipe Ross Burton
2025-07-28 16:16   ` Patchtest results for " patchtest
2025-07-29  8:20 ` Mathieu Dubois-Briand [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=DBOE54WLIIIG.3RM6KQUS65VQ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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