Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rust is self-hosted and because the compiler typically uses new language features as soon as they become available it can only be built with the previous minor version of Rust. This makes Rust notoriously hard to bootstrap.
Its bootstrap graph looks like this:
You can obtain this graph locally by running
guix graph rust | xdot -
Changes to the build environment
Changes to transitive build dependencies
Excluding the Rust bootstrap chain shown above.
I haven't tested this yet, but going by the estimates from this post I would expect that this adds roughly 12 hours to the time it takes to bootstrap Monero on a modern 12-core processor.
mrustc is working on adding support for Rust 1.74, which would shorten the bootstrap chain considerably.
This change introduces cross-architecture non-determinism. This means that cross-compiling using Rust from a different host architectures to a common target will not produce bit-identical output. This effectively means that participants in the verified reproduction process must build on a
x86_64
host. Unfortunately, reproducibility does not seem like a particularly high priority for the Rust project.