-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building Rust from source with x.py dist
uses binary components
#90555
Comments
The Cargo archive contains |
Rustc is self-hosted, which means it needs a rust compiler to build itself so by default it downloads the previous version. See the rustc-dev guide for an explanation of the build process. If you want to bootstrap from a C compiler you can start with mrustc, e.g. that's what guix does (they have updated their workflow since that blogpost). |
Thank you. We only have Rust 1.52.1 in our distribution (MarIuX), so we stay with |
Hmm,
(From a cursory glance, I do not see a difference to |
|
After working around the problems described in issue #90562, the build fails when using Rust 1.52.1.
Now building:
No idea, why toml is required to build a rustc 1.56.1. |
Like I said, it requires a one-older rust, the previous version. I.e. Building 1.56 requires 1.55 |
In issue #86436, @Mark-Simulacrum commented:
I tested
./x.py dist
with Rust 1.56.1, but unfortunately, it does not build every component from source, but downloads rust-std, rustc and cargo 1.55.0, containing the binaries.Can the already installed Rust in the system be used instead?
Otherwise,
x.py build
should be the supported way for distributions to build Rust.The text was updated successfully, but these errors were encountered: