linux/poky.git/meta/recipes-devtools/rust/files, branch walnascar-next

rust: Oe-selftest changes for rust v1.84.1

2025-03-27T13:41:58+00:00

Ignore the failing unit test. The tidy check failed due to a typo, which was already reported and fixed in the Rust upstream. Upstream-Status: Backport [https://github.com/rust-lang/rust/commit/8e7734978245522cbbd14e53e08e888faf031ded] (From OE-Core rev: 94a244a14075ead1b3b5e966c0fe713cd448cad8) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Fix build failure when multilibs are enabled

2025-03-27T13:41:58+00:00

When multilibs are enabled, building rust is failing because of the following commit https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e with stage1/rustc cannot able to find dependent *.so files. The issue is been fixed inrust-master with the following commit by passing the necessary library paths before executing stage1/rustc Upstream-Status: Backport [https://github.com/rust-lang/rust/commit/139d6ba054a1a4cc5fe64981ad46fd5547bd4916] (From OE-Core rev: ab29b970ba7e08eabca92018d103af5f249ed2c5) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Upgrade 1.83.0->1.84.1

2025-03-27T13:41:58+00:00

Rust stable version updated to 1.84.1. https://blog.rust-lang.org/2025/01/30/Rust-1.84.1.html Renamed and modified the below patch to adapt the new version. rv32-cargo-rustix-0.38.37-fix.patch->rv32-cargo-rustix-0.38.38-fix.patch Modified the below patches to adapt the new version. repro-issue-fix-with-cc-crate-hashmap.patch revert-link-std-statically-in-rustc_driver-feature.patch Dropped the below patches : 0001-NFC-fix-build-failure-100993.patch https://github.com/llvm/llvm-project/commit/6ee49080e4bb43efe7ede10bed15935853bbd434 revert-Zdual-proc-macros-additional-check.patch Issue is fixed in rust-master and the fix is backported in the subsequent patch of the series. (From OE-Core rev: 4265f668de8c6708cb3a003ad655559031724149) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Oe-selftest changes for rust v1.83.0

2025-03-05T21:26:54+00:00

Few unit tests are failing for x86_64 arch. Ignore the failing unit tests. Upstream-Status: Pending (From OE-Core rev: c71f9efc3140d279813ff6eb474fdbf5e677e348) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Upgrade 1.82.0->1.83.0

2025-03-05T21:26:54+00:00

Rust stable version updated to 1.83.0. https://blog.rust-lang.org/2024/11/28/Rust-1.83.0.html Renamed and modified the below patch to adapt the new version. rv32-cargo-rustix-0.38.34-fix.patch->rv32-cargo-rustix-0.38.37-fix.patch Modified the below patches to adapt the new version. repro-issue-fix-with-cc-crate-hashmap.patch revert-link-std-statically-in-rustc_driver-feature.patch Dropped: zlib-off64_t.patch https://github.com/madler/zlib/commit/a566e156b3fa07b566ddbf6801b517a9dba04fa3kq Because of the following commit , https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e when we enable lib32, getting build failure because there is a check for target support for "-Zdual-proc-macros" flag not functioning properly when lib32 is enabled in the build environment. So for now reverting this commit and bring back the previous behavior, where the "-Zdual-proc-macros" flag is always added for building proc macros, regardless of the target architecture's support. This would bypass the check introduced in the patch, allowing the build to proceed without error, even when building for a 64-bit architecture with lib32 enabled. (From OE-Core rev: 40d8dafdf556d7ce79c12a6de872193be9a0928a) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Oe-selftest changes for rust v1.82.0

2025-02-20T11:57:49+00:00

A few tests are getting failed with x86 arch.The unsupported/failing tests are added to the exclude list and ignore the failing unit tests. Upstream-Status: Pending (From OE-Core rev: b1340173be2a3a91fbb135eb0e24e50c3b996425) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: oe-selftest issue fix with v1.82

2025-02-20T11:57:49+00:00

A new feature "Link std statically in rustc_driver" was introduced in rust_1.82 [https://github.com/rust-lang/rust/pull/122362],and which is causing the below failure in oe-selftest. Running unittests src/main.rs (build/x86_64-unknown-linux-gnu/stage1-rustc/ x86_64-poky-linux-gnu/release/deps/rustc_main-92223b15c9f2d827) uploaded ".../build/x86_64-unknown-linux-gnu/stage1-rustc/x86_64-poky-linux-gnu/ release/deps/rustc_main-92223b15c9f2d827", waiting for result /tmp/work/test4056/rustc_main-92223b15c9f2d827: error while loading shared libraries: librustc_driver-fb0866b1cd913c20.so: cannot open shared object file: No such file or directory The rustc_main binary depends on the librustc_driver-*.so file. However, this file has not been copied to QEMU. If we manually copy the file into QEMU and export the LD_LIBRARY_PATH, the issue does not occur. Issue reprorted to upstream and reverted the buggy code as a workaround. Upstream-Status: Inappropriate [reported at https://github.com/rust-lang/rust/issues/136237] (From OE-Core rev: 977bd1a10771a6588e596e1bbfd49e9af659aa4a) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: Upgrade 1.81.0->1.82.0

2025-02-20T11:57:49+00:00

Rust stable version updated to 1.82.0. https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html Renamed the below patch to adapt the new version. rv32-cargo-rustix-0.38.28-fix.patch->rv32-cargo-rustix-0.38.34-fix.patch Dropped: rv32-rustix-libc-backend.patch [addressed with rv32-cargo-rustix-0.38.34-fix.patch] (From OE-Core rev: cfa431e734a642796140347f09c3c54b41a7bb75) Signed-off-by: Deepesh Varatharajan Signed-off-by: Richard Purdie

rust: restore parallel builds, disable lto only for rustdoc

2025-02-05T12:49:56+00:00

The original reproducibility fix was problematic for a couple reasons: - disabling both lto and parallel builds had an unfortunate effect of nearly doubling rust-native and rust build times (which are slow to begin with). Disabling lto hurts runtime performance too. - both of these things were done for the *entire build*, while the only problematic item is the librustdoc crate. - lto=off option in config.toml has an effect only on building rustc (the compiler itself), and doesn't help with rustdoc reproducibility. Actual fix is the codegen-units setting, which indirectly disables lto via giving llvm only one unit to work with at a time. After some digging, here's a more targeted fix for the problem. Why librustdoc is non-reproducible, but not anything else remains a mystery, hidden deep in rust-llvm's lto optimization code. (From OE-Core rev: a1977407a88a2004c3a6d2dba1d5bfe1aa1664b2) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

rust: increase test timeout again

2025-01-20T13:38:59+00:00

Fixes [YOCTO #15625] The first attempt to get around the timeout was to double it from 5000 to 10000, which doesn't seem to be enough. Let's try to fix this by extending the timeout by a factor of 10. (From OE-Core rev: fb19e038582a2bfc414465ef396c30197f67128f) Signed-off-by: Adrian Freihofer Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie