-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Ensure LLVM is in the link path for rustc tools #70123
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Seems good to me, and presuming it works for you then great! It looks like this is just a straight propagation of current logic/improvement on the status quo though. @bors r+ |
📌 Commit e1a6a30 has been approved by |
🌲 The tree is currently closed for pull requests below priority 5, this pull request will be tested once the tree is reopened |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Hmm, failed in bootstrap's own tests. I can reproduce locally, but it's not helpful:
I'll investigate more tomorrow... @bors r- |
OK, in a debugger I found the silence was because the test exits via
I pushed a new commit which should be more robust about missing llvm-config. |
r=me with CI passing, just in case |
@bors r=Mark-Simulacrum |
📌 Commit 3a2a442 has been approved by |
Rollup of 8 pull requests Successful merges: - rust-lang#69080 (rustc_codegen_llvm: don't generate any type debuginfo for -Cdebuginfo=1.) - rust-lang#69940 (librustc_codegen_llvm: Replace deprecated API usage) - rust-lang#69942 (Increase verbosity when suggesting subtle code changes) - rust-lang#69968 (rustc: keep upvars tupled in {Closure,Generator}Substs.) - rust-lang#70123 (Ensure LLVM is in the link path for rustc tools) - rust-lang#70159 (Update the bundled wasi-libc with libstd) - rust-lang#70233 (resolve: Do not resolve visibilities on proc macro definitions twice) - rust-lang#70286 (Miri error type: remove UbExperimental variant) Failed merges: r? @ghost
This is a follow-up to rust-lang#70123, which added `llvm-config --libdir` to the `LIBRARY_PATH` for rustc tools. We need the same for "run-make-fulldeps" and "ui-fulldeps" tests which depend on compiler libraries, implicitly needing to link to `-lLLVM` as well.
…rk-Simulacrum Ensure LLVM is in the link path for "fulldeps" tests This is a follow-up to rust-lang#70123, which added `llvm-config --libdir` to the `LIBRARY_PATH` for rustc tools. We need the same for "run-make-fulldeps" and "ui-fulldeps" tests which depend on compiler libraries, implicitly needing to link to `-lLLVM` as well.
…rk-Simulacrum Ensure LLVM is in the link path for "fulldeps" tests This is a follow-up to rust-lang#70123, which added `llvm-config --libdir` to the `LIBRARY_PATH` for rustc tools. We need the same for "run-make-fulldeps" and "ui-fulldeps" tests which depend on compiler libraries, implicitly needing to link to `-lLLVM` as well.
The build script for
rustc_llvm
outputs LLVM information incargo:rustc-link-lib
andcargo:rustc-link-search
so the compiler can be linked correctly. However, while the lib is carried along in metadata, the search paths are not. So when cargo is invoked again later for rustc tools, they'll also try to link with LLVM, but the necessary paths may be left out.Rustbuild can use the environment to set the LLVM link path for tools --
LIB
for MSVC toolchains andLIBRARY_PATH
for everyone else.Fixes #68714.