public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <deepesh.varatharajan@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] rust: dynamically link with llvm for all rust variants
Date: Wed, 11 Mar 2026 10:13:10 +0100	[thread overview]
Message-ID: <DGZU61EDNZ2W.1DOR2YWGZUYFE@bootlin.com> (raw)
In-Reply-To: <131089.1773216425426295510@lists.openembedded.org>

On Wed Mar 11, 2026 at 9:07 AM CET, Deepesh via lists.openembedded.org Varatharajan wrote:
> Hi Alex,
>
> This change need tweaks in rust.py and rust recipe to support multilib builds.
> Without tweaks rust selftest and rust multilib builds will fail.
>
> Required changes can be found here :
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=deepesh/sunil-rust-issue&id=44ce23e12e411ef9a1724e79c2b6ac6d5f0ddedc
>
> Regards,
> Deepesh

Hi Alex, Deepesh,

I believe it is related to this error?

/tmp/work/test4341/rustc_codegen_llvm-e21c84994fd391cb: error while loading shared libraries: libLLVM.so.21.1: cannot open shared object file: No such file or directory
error: test failed, to rerun pass `-p rustc_codegen_llvm --lib`
https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/1177
https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/3286

Thanks,
Mathieu

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



  parent reply	other threads:[~2026-03-11  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 18:13 [PATCH] rust: dynamically link with llvm for all rust variants Alexander Kanavin
2026-03-11  8:07 ` Varatharajan, Deepesh
2026-03-11  9:10   ` [OE-core] " Alexander Kanavin
2026-03-11  9:13   ` Mathieu Dubois-Briand [this message]
2026-03-11 10:40     ` Deepesh Varatharajan

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=DGZU61EDNZ2W.1DOR2YWGZUYFE@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=deepesh.varatharajan@windriver.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