-
-
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
Windows nightly binaries statically link against LLVM #29981
Comments
Anybody knows what's up? |
This should have been closed with #30033, but I just discovered the same issue applies to Windows:
|
This one seems more troublesome. Running |
Tentatively adding to the 1.1 milestone since this is a regression since 1.0. @staticfloat @eli-schwartz @vchuravy @vtjnash any ideas? |
I think Tim's findings are why we hardcoded the correct value (prior to #29446) |
Ouch. Seems like it would make more sense, though, to ensure the llvm toolchain is in healthy working order. If you're moving things around by hand in the llvm build configuration, it would likely be a good idea to fix it too... is it simply a matter of creating the symlinks on every OS? BTW looking at the source for llvm-config.cpp it looks like this hardcodes a |
Yeah, the problem we found is that the llvm toolchain doesn't have a health working order. I agree we should try to fix this upstream as you mentioned. In the meantime, we can put your fix behind a |
Maybe related: I made a PR upstream two years ago to restore support for custom install dirs. See https://reviews.llvm.org/D28234. |
Any update on this as the last issue blocking 1.1 release? |
Fixed (worked around) by #30459. |
As noted in JuliaLang#29981 and JuliaLang#30459, `llvm-config` is broken on Darwin, and sadly hasn't been fixed since then. Building Julia on Darwin with `USE_SYSTEM_LLVM` doesn't currently work, as calls to `llvm-config` produce the wrong flags. This PR fixes that.
i.e. the nightly binaries do not show
LLVM.dylib
in the output ofLibdl.dllist()
...The library is definitely there though, and suspiciously
libjulia
has grown with 40M:Looks like we've reverted to statically linking LLVM, presumably unintendedly since we're still shipping
LLVM.dylib
?Discovered while debugging LLVM.jl, which requires a dynamically-linked
libLLVM
and finds that library by looking at the output ofLibdl.dllist()
.I can do a bisect on the csail macmini, but that will take a while, and maybe somebody already knows what's up by the looks of this issue.
cc @staticfloat
The text was updated successfully, but these errors were encountered: