RUST 1.95.0 - WIP
We are facing several issues during this upgrade process because of recent upstream Rust changes have made building rustc for custom targets as unstable.
- Issue 1: Destabilise target-spec-json [Fixed]
Custom target require -Zunstable-options
https://github.com/rust-lang/rust/pull/150151 <https://github.com/rust-lang/rust/pull/150151>
https://github.com/rust-lang/rust/pull/151534 <https://github.com/rust-lang/rust/pull/151534>
Fix commits:
https://github.com/rust-lang/rust/issues/151729 <https://github.com/rust-lang/rust/issues/151729>
https://github.com/rust-lang/rust/pull/152677 <https://github.com/rust-lang/rust/pull/152677>
- Issue 2: Rust-dependent packages failures [Fixed]
The librsvg, python3-maturin are failued due to -Zunstable-options
Fix commits:
https://github.com/PyO3/setuptools-rust/pull/587 <https://github.com/PyO3/setuptools-rust/pull/587>
https://github.com/lu-zero/cargo-c/pull/537 <https://github.com/lu-zero/cargo-c/pull/537>
- Issue 3: Failures with oe-selftest [Fixed]
Fix commit:
https://github.com/rust-lang/rust/pull/154993 <https://github.com/rust-lang/rust/pull/154993>
- Issue 4: rustc need -Zunstable-options for every invocation [WIP]
When rustc is built for custom targets, the resulting compiler requires the -Zunstable-options flag for every invocation of rustc binary.
For e.g., rustc -vV -Zunstable-options
We tried to workaround this issue with a wrapper function but facing a few issues with sdk env and currently discussing with upstream about proper fix.
https://github.com/rust-lang/rust/issues/155963 <https://github.com/rust-lang/rust/issues/155963>
Upstream suggested registering our targets as another workaround. While this is technically possible but it is not practical.
Details were documented here -
https://github.com/rust-lang/rust/issues/155963#issuecomment-4406456742