Skip to content
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

Merged
merged 1 commit into from
Jan 20, 2021
Merged

Remove "Skipping LLVM build" section #1030

merged 1 commit into from
Jan 20, 2021

Conversation

jyn514
Copy link
Member

@jyn514 jyn514 commented Jan 20, 2021

download-ci-llvm is available and enabled by default for all tier 1
platforms (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.

`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.
@jyn514
Copy link
Member Author

jyn514 commented Jan 20, 2021

Well, "enabled by default" if you set profile = "compiler". I haven't changed the actual default yet.

@jyn514 jyn514 merged commit 4e48f42 into rust-lang:master Jan 20, 2021
@jyn514 jyn514 deleted the llvm branch January 20, 2021 18:45
Comment on lines -218 to -237
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`.
Copy link
Member

@camelid camelid Jan 21, 2021

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?

Copy link
Member Author

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.

camelid added a commit to camelid/rustc-dev-guide that referenced this pull request Feb 21, 2021
They were removed in rust-lang#1030, but are still useful.
jyn514 pushed a commit that referenced this pull request Feb 26, 2021
They were removed in #1030, but are still useful.
camelid added a commit that referenced this pull request Dec 29, 2021
The section was removed in #1030 and re-added in a different place in
2d42cf7.
pierwill pushed a commit that referenced this pull request Dec 29, 2021
The section was removed in #1030 and re-added in a different place in
2d42cf7.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants