Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork841
Open
Description
I'm motivated to post this to help with the "on-boarding".
Instructions say to run:
$ cargo install cargo-binutils rustfiltNot sure exactly why, but this failed for me with:
error: failed to compile `cargo-binutils v0.3.6`Caused by: package `cargo-platform v0.1.8` cannot be built because it requires rustc 1.73 or newer, while the currently active rustc version is 1.66.0-nightly Try re-running cargo install with `--locked`I happened to havenightly-2022-10-13-x86_64-unknown-linux-gnu installed, which I think corresponds torustc 1.66.0-nightly (c0983a9aa 2022-10-12), but this isn't my active toolchain normally. It's just installed.
So I re-ran with--locked and it worked:
$ cargo install cargo-binutils rustfilt --locked... Installed package `cargo-binutils v0.3.6` (executables `cargo-cov`, `cargo-nm`, `cargo-objcopy`, `cargo-objdump`, `cargo-profdata`, `cargo-readobj`, `cargo-size`, `cargo-strip`, `rust-ar`, `rust-cov`, `rust-ld`, `rust-lld`, `rust-nm`, `rust-objcopy`, `rust-objdump`, `rust-profdata`, `rust-readobj`, `rust-size`, `rust-strip`)Assuming that this was the right thing to do, would it make sense to suggest that users always run with--locked, to ensure that the correct versions are picked up?
Metadata
Metadata
Assignees
Labels
No labels