-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "Skipping LLVM build" section #1030
Conversation
`download-ci-llvm` is available and enabled by default for all tier 1 platforms, so there is no need to change it. Using system LLVM over CI llvm is still supported, but is not recommended. Building LLVM from source is still supported. This also notes that you need to explicitly disable downloading LLVM when updating the submodule.
Well, "enabled by default" if you set |
Another alternative is to use LLVM already installed on your computer. This is | ||
specified in the `target` section of `config.toml`: | ||
|
||
```toml | ||
[target.x86_64-unknown-linux-gnu] | ||
llvm-config = "/path/to/llvm/llvm-7.0.1/bin/llvm-config" | ||
``` | ||
|
||
We have observed the following paths before, which may be different from your system: | ||
|
||
- `/usr/bin/llvm-config-8` | ||
- `/usr/lib/llvm-8/bin/llvm-config` | ||
|
||
Note that you need to have the LLVM `FileCheck` tool installed, which is used | ||
for codegen tests. This tool is normally built with LLVM, but if you use your | ||
own preinstalled LLVM, you will need to provide `FileCheck` in some other way. | ||
On Debian-based systems, you can install the `llvm-N-tools` package (where `N` | ||
is the LLVM version number, e.g. `llvm-8-tools`). Alternately, you can specify | ||
the path to `FileCheck` with the `llvm-filecheck` config item in `config.toml` | ||
or you can disable codegen test with the `codegen-tests` item in `config.toml`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jyn514 Was this supposed to be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, using system llvm is no longer recommended. There's a short section on it in config.toml.example, I don't think it needs its own section in the guide.
They were removed in rust-lang#1030, but are still useful.
They were removed in #1030, but are still useful.
download-ci-llvm
is available and enabled by default for all tier 1platforms (since rust-lang/rust#80932), so there is no need to change it.
Using system LLVM over CI llvm is still supported, but is not recommended. Building LLVM from
source is still supported.
This also notes that you need to explicitly disable downloading LLVM
when updating the submodule.