diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-10-19 21:38:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-19 21:38:41 +0200 |
| commit | e85def73b54a3b4614980d5d3e74a2cfa94b8a57 (patch) | |
| tree | 3e677484cf5c466b6dda2b4174cf05386ab52c47 /compiler/rustc_codegen_gcc | |
| parent | 12775ce16a4449c0f04cbce14efc56ac8d9ed39a (diff) | |
| parent | 5b7bd2fed899b7966a09a6d5552a2e1985bc7526 (diff) | |
| download | rust-e85def73b54a3b4614980d5d3e74a2cfa94b8a57.tar.gz rust-e85def73b54a3b4614980d5d3e74a2cfa94b8a57.zip | |
Rollup merge of #103246 - ferrocene:pa-rust-analyzer-hosts, r=Mark-Simulacrum
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. The problem can be reproduced by running: ``` ./x build src/tools/rust-analyzer --target x86_64-unknown-linux-gnu,aarch64-unknown-none ```
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions