diff options
| author | Pietro Albini <pietro.albini@ferrous-systems.com> | 2022-10-19 14:33:17 +0200 |
|---|---|---|
| committer | Pietro Albini <pietro.albini@ferrous-systems.com> | 2022-10-19 14:33:17 +0200 |
| commit | 5b7bd2fed899b7966a09a6d5552a2e1985bc7526 (patch) | |
| tree | cada6989b699da06a68f7744254af531bcfd4648 /src/bootstrap | |
| parent | 5605ed85363345f3def5da6b1ead2ac0b803bfe7 (diff) | |
| download | rust-5b7bd2fed899b7966a09a6d5552a2e1985bc7526.tar.gz rust-5b7bd2fed899b7966a09a6d5552a2e1985bc7526.zip | |
mark rust-analyzer as a host-only tool
All tools meant to be shipped with host toolchains only should be marked as `ONLY_HOSTS = true`, but rust-analyzer was marked as `ONLY_HOSTS = false` incorrectly. This meant that bootstrap attempted to build rust-analyzer for cross-compilation-only targets, causing errors because libstd is not present on some of them. It will still be possible to cross-compile rust-analyzer by passing a different --host flag to ./x, like you can cross-compile other tools.
Diffstat (limited to 'src/bootstrap')
| -rw-r--r-- | src/bootstrap/tool.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/bootstrap/tool.rs b/src/bootstrap/tool.rs index d6e7f787270..eec74b2675a 100644 --- a/src/bootstrap/tool.rs +++ b/src/bootstrap/tool.rs @@ -698,7 +698,7 @@ pub struct RustAnalyzer { impl Step for RustAnalyzer { type Output = Option<PathBuf>; const DEFAULT: bool = true; - const ONLY_HOSTS: bool = false; + const ONLY_HOSTS: bool = true; fn should_run(run: ShouldRun<'_>) -> ShouldRun<'_> { let builder = run.builder; @@ -742,7 +742,7 @@ pub struct RustAnalyzerProcMacroSrv { impl Step for RustAnalyzerProcMacroSrv { type Output = Option<PathBuf>; const DEFAULT: bool = true; - const ONLY_HOSTS: bool = false; + const ONLY_HOSTS: bool = true; fn should_run(run: ShouldRun<'_>) -> ShouldRun<'_> { let builder = run.builder; |
