diff options
| author | bors <bors@rust-lang.org> | 2025-03-09 04:31:52 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-03-09 04:31:52 +0000 |
| commit | a96fa317d78c78a9de996afd317603c6970efc0d (patch) | |
| tree | 9ad4fa8bd431c05b85c886b5289a209f5fc3b12b /compiler/rustc_hir/src | |
| parent | 446649d46383734e9e047d072a482720216dd59c (diff) | |
| parent | f677bab5dae958a6853f9298697780975199a64c (diff) | |
| download | rust-a96fa317d78c78a9de996afd317603c6970efc0d.tar.gz rust-a96fa317d78c78a9de996afd317603c6970efc0d.zip | |
Auto merge of #137541 - onur-ozkan:fix-cargo-clippy-bin, r=jieyouxu
add `tool::CargoClippy` and `tool::Cargofmt` binary to target sysroot When running `x build clippy`, we expect `stage1-tool-bin/cargo-clippy` and `stage2/bin/cargo-clippy` to be the same, but they aren't. This happens because `tool::CargoClippy` doesn't place its binary in the `stage2` directory. As a result, `stage1-tool-bin/cargo-clippy` comes from `tool::CargoClippy`, while `stage2/bin/cargo-clippy` comes from `tool::Cargo`. Same applies for `tool::Cargofmt`. This PR fixes the issue by adding `tool::CargoClippy` and ``tool::Cargofmt`` binaries to the expected sysroot and makes sure both directories share the same binary. To test this, run `x build --stage 2 compiler clippy rustfmt`, link the stage2 sysroot with rustup, and then call `cargo +stage2 fmt` and `cargo +stage2 clippy` on any rust project (it wouldn't work without this PR).
Diffstat (limited to 'compiler/rustc_hir/src')
0 files changed, 0 insertions, 0 deletions