> I believe this is breaking build on some platforms. Maybe all ARM 32 > bits? > > ERROR: rust-1.98.1-r0 do_install: Execution of '/srv/pokybuild/yocto-worker/beaglebone-alt/build/build/tmp/work/cortexa8t2hf-neon-poky-linux-gnueabi/rust/1.98.1/temp/run.do_install.3194208' failed with exit code 1 > ... > | error[E0658]: use of unstable library feature `stdarch_arm_neon_intrinsics` > | --> /rust/deps/simd-adler32-0.3.9/src/imp/neon.rs:23:7 > | | > | 23 | use core::arch::arm::*; > | | ^^^^^^^^^^^^^^^ > | | > | = note: see issue #111800 <https://github.com/rust-lang/rust/issues/111800> for more information > | = help: add `#![feature(stdarch_arm_neon_intrinsics)]` to the crate attributes to enable > | = note: this compiler was built on 2026-09-01; consider upgrading it if it is out of date > ... > | ------------- > | error: could not compile `simd-adler32` (lib) due to 67 previous errors > | warning: build failed, waiting for other jobs to finish... > ... > > Can you have a look at the issue?
@Mathieu, thanks for the feedback, yeah I could replicate it when targeting "machine/beaglebone-yocto", seems like rust-analyzer is resolving a newer simd-adler32 (0.3.9) than the rustc/std build (0.3.7) which fails on NEON arm32 during build. It might be that the std/compiler build runs with full unstable-feature access, whereas the analyzer tool does not. Removing the target installation of the tool seemed to fix the problem. > One thing that's concerning here: We're seeing a compiler error message > during do_install. That suggests we're missing a build step in > do_compile, as things should already be built by the time we get to > do_install. > > That may be a pre-existing issue for the rust recipe, if it is then we > should make sure there is a bug filed for it. @Paul, I agree this is pre-existing, the rust recipe has an empty do_compile(), and all building happens in do_install via "rust_runx install", which runs x.py install (build + install in one step). > We definitely want to take new features that people will use, but we > should avoid enabling things just for the sake of it if there is no > clear use case. > > Are you using rust-analyzer from the SDK? Yes, so based on the conversation above seems like the most reasonable is to install only for class-nativesdk.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247128): https://lists.openembedded.org/g/openembedded-core/message/247128 Mute This Topic: https://lists.openembedded.org/mt/121527283/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
