rustbuild: allow dynamically linking LLVM #37822
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The makefiles and `mklldeps.py` called `llvm-config --shared-mode` to find out if LLVM defaulted to shared or static libraries, and just went with that. But under rustbuild, `librustc_llvm/build.rs` was assuming that LLVM should be static, and even forcing `--link-static` for 3.9+. Now that build script also uses `--shared-mode` to learn the default, which should work better for pre-3.9 configured for dynamic linking, as it wasn't possible back then to choose differently via `llvm-config`. Further, the configure script now has a new `--enable-llvm-link-shared` option, which allows one to manually override `--link-shared` on 3.9+ instead of forcing static.
Contributor
|
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
Member
Author
Member
|
Looks good to me! It appears though that |
Member
Author
|
Ah, I hadn't noticed that |
Member
|
Ah ok, either's fine by me! |
There are now four static/shared scenarios that can happen for the supported LLVM versions: - 3.9+: By default use `llvm-config --link-static` - 3.9+ and `--enable-llvm-link-shared`: Use `--link-shared` instead. - 3.8: Use `llvm-config --shared-mode` and go with its answer. - 3.7: Just assume static, maintaining the status quo.
Member
Author
|
OK, that push will hopefully help 3.7, and I updated the PR summary with the four linking scenarios. |
Member
Author
|
Hmm, those latest travis jobs don't look like they actually tried anything... |
Member
|
@bors: r+ Thanks! |
Collaborator
|
📌 Commit f324037 has been approved by |
Collaborator
|
⌛ Testing commit f324037 with merge b1da18f... |
bors
added a commit
that referenced
this pull request
Nov 19, 2016
rustbuild: allow dynamically linking LLVM The makefiles and `mklldeps.py` called `llvm-config --shared-mode` to find out if LLVM defaulted to shared or static libraries, and just went with that. But under rustbuild, `librustc_llvm/build.rs` was assuming that LLVM should be static, and even forcing `--link-static` for 3.9+. Now that build script also uses `--shared-mode` to learn the default, which should work better for pre-3.9 configured for dynamic linking, as it wasn't possible back then to choose differently via `llvm-config`. Further, the configure script now has a new `--enable-llvm-link-shared` option, which allows one to manually override `--link-shared` on 3.9+ instead of forcing static. Update: There are now four static/shared scenarios that can happen for the supported LLVM versions: - 3.9+: By default use `llvm-config --link-static` - 3.9+ and `--enable-llvm-link-shared`: Use `--link-shared` instead. - 3.8: Use `llvm-config --shared-mode` and go with its answer. - 3.7: Just assume static, maintaining the status quo.
Collaborator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The makefiles and
mklldeps.pycalledllvm-config --shared-modetofind out if LLVM defaulted to shared or static libraries, and just went
with that. But under rustbuild,
librustc_llvm/build.rswas assumingthat LLVM should be static, and even forcing
--link-staticfor 3.9+.Now that build script also uses
--shared-modeto learn the default,which should work better for pre-3.9 configured for dynamic linking, as
it wasn't possible back then to choose differently via
llvm-config.Further, the configure script now has a new
--enable-llvm-link-sharedoption, which allows one to manually override
--link-sharedon 3.9+instead of forcing static.
Update: There are now four static/shared scenarios that can happen
for the supported LLVM versions:
llvm-config --link-static--enable-llvm-link-shared: Use--link-sharedinstead.llvm-config --shared-modeand go with its answer.