From: Harish.Sadineni@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com
Subject: [wrynose][PATCH] kernel-yocto-rust: skip recipe for riscv64 when Rust support is enabled
Date: Tue, 11 Aug 2026 04:58:55 -0700 [thread overview]
Message-ID: <20260811115855.4033577-1-Harish.Sadineni@windriver.com> (raw)
From: Harish Sadineni <Harish.Sadineni@windriver.com>
Kernel Rust support on riscv64 requires building the kernel with Clang.
Since Wrynose does not provide Clang toolchian support for kernel
builds, skip the recipe when TARGET_ARCH is riscv64.
This avoids attempting an unsupported kernel Rust build and provides a
clear parse-time error explaining the limitation.
Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com>
---
meta/classes-recipe/kernel-yocto-rust.bbclass | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/meta/classes-recipe/kernel-yocto-rust.bbclass b/meta/classes-recipe/kernel-yocto-rust.bbclass
index 49f2bfc1ae..6be97c2db8 100644
--- a/meta/classes-recipe/kernel-yocto-rust.bbclass
+++ b/meta/classes-recipe/kernel-yocto-rust.bbclass
@@ -25,3 +25,12 @@ do_kernel_configme:append () {
# More details in: https://lists.openembedded.org/g/openembedded-core/message/229336
# Disable ccache for kernel build if kernel rust support is enabled to workaround this.
CCACHE_DISABLE ?= "1"
+
+python () {
+ if d.getVar('TARGET_ARCH') == 'riscv64' :
+ raise bb.parse.SkipRecipe(
+ "Rust support in the kernel on riscv64 requires kernel to build with clang, "
+ "Wrynose doesn't have clang toolchain support for kernel. See "
+ "https://docs.kernel.org/rust/arch-support.html for details."
+ )
+}
--
2.53.0
next reply other threads:[~2026-08-11 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 11:58 Harish.Sadineni [this message]
2026-09-03 21:34 ` [OE-core] [wrynose][PATCH] kernel-yocto-rust: skip recipe for riscv64 when Rust support is enabled Yoann Congal
2026-09-04 11:40 ` Harish Sadineni
2026-09-08 6:52 ` Yoann Congal
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=20260811115855.4033577-1-Harish.Sadineni@windriver.com \
--to=harish.sadineni@windriver.com \
--cc=Sundeep.Kokkonda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.