-
-
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
julia 1.9.0-beta2 fails to build from source on macOS #48057
Comments
If I read the LLVM commit right, that was fixed in LLVM 15.0.0, but Julia 1.9.0-beta2 uses LLVM 14.0.5. |
I think we can backport that patch, and we might want allow to user to use the system |
For the record, this affects building Julia on all macOS versions when Xcode 14 / Apple clang 14 is used (both macOS 12 and 13, and both Intel and ARM processors). |
Huh, I am building Julia all the time on macOS 12 with Xcode 14 / Apple clang 14 installed. So perhaps there is more to the story? |
@fingolfin do you use
|
No, I don't -- the fact that you do (and the full build instructions) seems like critical information to include in the issue description, though :-) |
[ Off-topic, but: Of course the fact that Homebrew does all these things is also why I tell all our users (i.e.: of a specific Julia package, I am not a core Julia developer) to avoid installing Julia via Homebrew or Debian or a bunch of other package managers; for us it is critical that the same libgmp, libmpfr, etc. etc. are used by Julia and by our BinaryBuild recipes, and Homebrew/Debian/etc break that assumption, which caused all kinds of subtle, hard to debug issues over the years ] |
In this case, it's none of the system versions that is causing the trouble, but the fact that Julia is actually using an outdated dependency :) if we built against LLVM 15, we would not have that issue. So there are two sides to that coin. |
At the time we started the release process for Julia 1.9 LLVM 14 was the currently released version. LLVM is for many projects a special dependency since it is extremely hard to support more than one version. Additionally moving to a new LLVM version is a work intensive process and often introduces new bugs, not something we want to do right before we cut a release. (LLVM 15 is particularly problematic since it will no longer support older Mac versions) We have two problems here. The first is what are the libraries that have this new Secondly the issue is that we can't assume that the user has Xcode installed, that's why the Julia is bundling LLD. Now there are two solutions here that might be feasible. Firstly we can backport that patch to our tree of LLVM. Secondly I can provide a build system flag to not use the bundled LLD and instead use the system linker. If Homebrew can guarantee that one is available at all times. |
That seems like the best outcome. This will fix things not only for Homebrew, but also other users. |
For our problem, #48235, this solution would work. |
I was looking for a solution to this but there is a question here. We could have a use system |
This is still occurring with 1.9.0-beta4 |
(I realize now we haven't done a new release since the PR that fixed this was merged) |
We are seeing the build failure on Homebrew CI at Homebrew/homebrew-core#119456
The error seems to be
lld: error: LC_DYLD_INFO_ONLY not found
.Possible related links:
The text was updated successfully, but these errors were encountered: