about summary refs log tree commit diff
path: root/src/test/run-pass/thinlto
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2016-11-19 08:08:26 -0800
committerGitHub <noreply@github.com>2016-11-19 08:08:26 -0800
commitb1da18fe9be180ecfcfb1691c4eb669c496996f5 (patch)
treefd9ae079f4132c999d84e2eed8d772d1bc56d6e7 /src/test/run-pass/thinlto
parentfb025b483a5ef96bba944055c47af620d2afb602 (diff)
parentf3240377e6ebdff032e9275aee8dd461e9866cbb (diff)
downloadrust-b1da18fe9be180ecfcfb1691c4eb669c496996f5.tar.gz
rust-b1da18fe9be180ecfcfb1691c4eb669c496996f5.zip
Auto merge of #37822 - cuviper:llvm-link-shared, r=alexcrichton
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.
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions