Open notdanilo opened 3 months ago
@rustbot label +Command-install +A-building-cargo-itself
This is expected, as documented in the Cargo Contributor Guide.
But when cargo is not run via rustup, the toolchain may change based on the directory. Since Cargo changes the directory for each compilation, this can cause different calls to rustc to use different versions.
You can see under ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ff-0.13.0/rust-toolchain
the ff
crate has a quite old MSRV. It doesn't recognize a relatively new --diagnostic-width
option from rustc.
The contributor guide also provides some workaround already. Setting RUSTC
or RUSTUP_TOOLCHAIN
might be good alternatives.
This is a gnarly problem that rustup and cargo are not a single binary, so Cargo doesn't know if it belongs to a toolchain. I don't think it is fixable at this moment, but leave this open for future reference.
Problem
Steps
Run this twice on cargo's repository:
Possible Solution(s)
No response
Notes
No response
Version