mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-27 01:04:03 +00:00
Rollup merge of #110121 - jyn514:check-stage1, r=ozkanonur
Fix `x check --stage 1` when download-rustc is enabled Helps with https://github.com/rust-lang/rust/issues/81930
This commit is contained in:
commit
6f2fd3e6a2
@ -271,9 +271,17 @@ impl Step for Rustc {
|
||||
false,
|
||||
);
|
||||
|
||||
let libdir = builder.sysroot_libdir(compiler, target);
|
||||
let hostdir = builder.sysroot_libdir(compiler, compiler.host);
|
||||
add_to_sysroot(&builder, &libdir, &hostdir, &librustc_stamp(builder, compiler, target));
|
||||
// HACK: This avoids putting the newly built artifacts in the sysroot if we're using
|
||||
// `download-rustc`, to avoid "multiple candidates for `rmeta`" errors. Technically, that's
|
||||
// not quite right: people can set `download-rustc = true` to download even if there are
|
||||
// changes to the compiler, and in that case ideally we would put the *new* artifacts in the
|
||||
// sysroot, in case there are API changes that should be used by tools. In practice,
|
||||
// though, that should be very uncommon, and people can still disable download-rustc.
|
||||
if !builder.download_rustc() {
|
||||
let libdir = builder.sysroot_libdir(compiler, target);
|
||||
let hostdir = builder.sysroot_libdir(compiler, compiler.host);
|
||||
add_to_sysroot(&builder, &libdir, &hostdir, &librustc_stamp(builder, compiler, target));
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user