-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Make llvmunwind depend on llvm #45380
Conversation
Our LLVMunwind is trailing our LLVM version so this now tightly couples them. We should upgrade LLVMUnwind to match the LLVM version first. |
Isn't that orthogonal to this PR? This is about the order with which we have to build the various dependencies. |
This enforces the right build order, in the case where both are built from source. It just fixes the build, but does not change the versions used or couple them any more than they already are. |
What I am saying is that linking LLVMUnwind12 against LLVM13 may not work. We use a standalone built of LLVMUnwind https://github.com/JuliaPackaging/Yggdrasil/blob/master/L/LLVMLibUnwind/common.jl |
Ah I see it just adds an ordering? But why is that necessary? These two libraries should be independent of each other |
They're not, because later in that file:
So this PR is only fixing a build failure, but not otherwise changing the already existing dependency. It is not, in other words, making things worse on that side. |
Can you build without setting the llvm-config path? |
If I remove
but otherwise appears to build without trouble. |
Should we merge? |
One test failure in
|
The same error is showing in an unrelated PR on freebsd64: #45435 |
@vchuravy merge? |
This is needed for source builds to work on macOS. Could it be merged, and possibly backported to 1.8 before release? |
I'm merging this since it should really not be an issue. |
As I said before I think this is wrong. Our builds of LLVMUnwind and LLVM proper are NOT linked. So the use of I don't know what the right solution is. My preferred solution is to build LLVMUnwind as part of LLVM so that these issues do not arise. But as the situation is this is a "pseudo"-fix. I do not have a Mac. @vtjnash this seems more in your wheel house. |
If it is ok, this helps us get past the current build failure on macs from source? In the meanwhile, can we separately open an issue to build LLVMUnwind the right way? |
Just a note that @vtjnash approved this PR. I'm marking it for backport so that the build for homebrew on mac can go through, whatever the longer term decision is. |
(cherry picked from commit 6ea9034)
Fixes #45379