-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Fix configure --llvm-root #6802
Comments
I'll be happy to test anything related to unbundling llvm. |
nominating feature-complete milestone |
Just a bug -- internal implementation issue. |
Fixing this would really help us to get rust into fedora. A bundled llvm is a major blocker. Tim Chevalier notifications@github.com schrieb: Just a bug -- internal implementation issue. — |
Sadly, until we get our patches into LLVM upstream we won't be able to do this. |
Well, I would think we could fix the |
Will the |
In theory all we need are the headers and libraries, the source shouldn't be necessary at all. |
--llvm-root is actually working fine for me on macos and linux (though i last checked it on linux about 2 months ago). I have llvm built with Building rustc with |
Indeed, we're using |
Remove workspace and fix dogfood (again) changelog: none In response to rust-lang/rust-clippy#6733 (comment)
Dogfood and CI fixes The CI fix is practically rust-lang#6829 rebased and squashed into one commit Dogfood fix is a follow up of rust-lang#6802 r? `@matthiaskrgr` for lintcheck changes (best reviewed with whitespace changes hidden) changelog: none
Rust currently uses a patched version of llvm. Some time ago, we added a
--llvm-root
option to configure (#1123), to allow the user to point the build at an LLVM outside the build tree.Some recent discussion on #4259 and on wiki packaging leads me to conclude that the
llvm-root
switch is broken.We may want to fix it, e.g. to test, once our patches have landed upstream, whether a new version of LLVM works.
(Also, I would be curious if there is a way to build the LLVM source once and share it amongst multiple clones of the Rust git repository. Doing that was the impetus for my interest in this matter, though in hindsight it is possible that
--llvm-root
never actually supported that use-case.)The text was updated successfully, but these errors were encountered: