From: Harish Sadineni <Harish.Sadineni@windriver.com>
To: Antonin Godard <antonin.godard@bootlin.com>,
openembedded-core@lists.openembedded.org
Cc: "MacLeod, Randy" <Randy.MacLeod@windriver.com>,
"Kokkonda, Sundeep" <sundeep.kokkonda@windriver.com>,
Alistair Francis <alistair23@gmail.com>
Subject: Re: [OE-core] [PATCH v4 00/16] Enable rust support for linux kernel
Date: Wed, 28 Jan 2026 23:04:12 +0530 [thread overview]
Message-ID: <9fcc4fbe-d575-46ee-8d16-08bca32d44d7@windriver.com> (raw)
In-Reply-To: <DFYCXSVMAPCN.R3OW6N5BF8ZJ@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 3049 bytes --]
On 1/26/2026 1:24 PM, Antonin Godard wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hi,
>
> On Thu Jan 22, 2026 at 3:24 PM CET, Antonin Godard via lists.openembedded.org wrote:
> [...]
>>> Thanks for reporting this.
>>> The error indicates that the linker is unable to locate libm.so.6 and
>>> libmvec.so.6 in the recipe sysroot.
>>> These libraries are normally provided by glibc, and this issue does not
>>> appear to be caused by our patches, as we are not able to reproduce it
>>> locally.
>>> Could you please re-test the series once more to confirm?
>>>
>>> Thanks,
>>> Harish
>> Ok, thanks for testing again on your side. It may have been related to another
>> commit on my branch as I'm not facing the issues again. I'll re-add the series
>> to my branch - sorry for the false alarm!
> Sorry, but after starting an a-full run with your series again, I started
> getting the same errors again:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3110
>
> I've launched an a-full build with the same branches minus your series and I
> don't see the errors anymore:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3115
>
> You can compare the branches used for the two builds by comparing:
>
> https://git.yoctoproject.org/poky-ci-archive/log/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3110
> https://git.yoctoproject.org/poky-ci-archive/log/?h=bitbake/autobuilder.yoctoproject.org/valkyrie/a-full-3110
> https://git.yoctoproject.org/poky-ci-archive/log/?h=meta-yocto/autobuilder.yoctoproject.org/valkyrie/a-full-3110
>
> vs.
>
> https://git.yoctoproject.org/poky-ci-archive/log/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3115
> https://git.yoctoproject.org/poky-ci-archive/log/?h=bitbake/autobuilder.yoctoproject.org/valkyrie/a-full-3115
> https://git.yoctoproject.org/poky-ci-archive/log/?h=meta-yocto/autobuilder.yoctoproject.org/valkyrie/a-full-3115
>
> Maybe your build uses some shared state which is why your builds pass?
>
> You can base off your test builds against my a-full-3110 branches above, that
> may help.
I was able to reproduce the issue locally.
Failure was happening due to Alistair Francis's patch from my v4 series
(https://lists.openembedded.org/g/openembedded-core/message/229769) when
applied together
with following patch "llvm: enable LLVMgold.so build by adding binutils
dependency(https://lists.openembedded.org/g/openembedded-core/message/229387)"
To avoid this issue, I am dropping Alistair Francis’s patch
(https://lists.openembedded.org/g/openembedded-core/message/229769<https://lists.openembedded.org/g/openembedded-core/message/229769>)
from my patch set.
We will send a v5 series tomorrow.
Thanks,
Harish
>
> Regards,
> Antonin
>
> --
> Antonin Godard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
[-- Attachment #2: Type: text/html, Size: 5513 bytes --]
prev parent reply other threads:[~2026-01-28 17:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 18:29 [PATCH v4 00/16] Enable rust support for linux kernel Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 01/16] linux-yocto: conditionally add clang/rust/bindgen-cli-native to DEPENDS Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 02/16] rust: Install the Rust source Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 03/16] rust: install Rust library sources for target & sdk Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 04/16] kernel-yocto: enable Rust kernel support via 'make rustavailable' Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 05/16] linux-yocto: enable Rust support in kernel configuration Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 06/16] kernel-yocto: Fix for buildpaths errors when rust is enabled for kernel Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 07/16] make-mod-scripts: split `HOSTCC` flag to align with to linux-yocto Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 08/16] kernel-yocto.bbclass: Disable ccache when rust-kernel is enabled Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 09/16] kernel-devsrc: copying rust-kernel source to $kerneldir/build Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 10/16] selftest/cases/runtime_test: Add test for Linux Rust sample Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 11/16] kernel.bbclass: Copy include/config/auto.conf in STAGING_KERNEL_BUILDDIR Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 12/16] kernel.bbclass: Export artifacts needed for out-of-tree Rust compilation Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 13/16] module.bbclass: Prepare out-of-tree rust module compilation Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 14/16] meta-skeleton: Add rust-out-of-tree-module recipe Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 15/16] make-mod-scripts: fix for buildpath issues with rust-out-of-tree compilation Harish.Sadineni
2026-01-20 18:29 ` [PATCH v4 16/16] runtime_test: Add rust-out-of-tree selftest Harish.Sadineni
2026-01-20 18:41 ` [PATCH v4 00/16] Enable rust support for linux kernel Sadineni, Harish
2026-01-21 15:16 ` [OE-core] " Antonin Godard
2026-01-22 11:53 ` Harish Sadineni
2026-01-22 14:24 ` Antonin Godard
2026-01-26 7:54 ` Antonin Godard
2026-01-28 17:34 ` Harish Sadineni [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=9fcc4fbe-d575-46ee-8d16-08bca32d44d7@windriver.com \
--to=harish.sadineni@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=alistair23@gmail.com \
--cc=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sundeep.kokkonda@windriver.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