riscv32 builds fail since AtomicI64 is not available in sync::atomic for
this architecture. Therefore it needs to be opted out and the way out is
to pass it by RUSTFLAGS, however rust target recipe overrides RUSTFLAGS
before exporting it so its better to piggy back on the variable its
using which is RUST_DEBUG_REMAP

Signed-off-by: Khem Raj <raj.k...@gmail.com>
---
 meta/recipes-devtools/rust/rust_1.64.0.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/rust/rust_1.64.0.bb 
b/meta/recipes-devtools/rust/rust_1.64.0.bb
index 1f9dbd3cce..b05f188d9c 100644
--- a/meta/recipes-devtools/rust/rust_1.64.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.64.0.bb
@@ -9,6 +9,7 @@ FILES:${PN}-dev = ""
 
 # Used by crossbeam_atomic.patch
 export TARGET_VENDOR
+RUST_DEBUG_REMAP:append:riscv32 = " --cfg crossbeam_no_atomic_64"
 
 do_compile () {
     rust_runx build --stage 2
-- 
2.38.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172006): 
https://lists.openembedded.org/g/openembedded-core/message/172006
Mute This Topic: https://lists.openembedded.org/mt/94464934/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to