-
Notifications
You must be signed in to change notification settings - Fork 22
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
res/local.jl
Inconsistency in commandline options with multiple vendor libraries installed
#170
Comments
This happens when loading multiple copies of LLVM. Julia's copy should be protected by this because of symbol versioning (@vchuravy can you confirm?), so is it possible you're either using a non-official Julia build (with SYSTEM_LLVM) or LD_PRELOADing a library that dynamically links against LLVM, or something similar? |
Yeah we should no longer get these from Julia normally, but of course most other LLVM are not hardened and I don't know how weak symbols will play with it |
But I don't recall if we got all this in place for 1.6 and LLVM 11 |
This error appeared with Julia 1.6 and 1.8. Peng then pointed me to not load the oneAPI module on the target system, but only load the Intel Compute Runtime. We have to use the system libraries. That resolved the issue. |
So I'm guessing |
I don't think there's anything actionable here, as it requires changes to how the libraries we load are compiled. |
Thanks for this script.
When running it on a system with both Intel CPU and GPUs, I get the following output:
This seems related to https://bugs.llvm.org/show_bug.cgi?id=30587
On such a system you can trigger by loading any runtime library:
Output:
The text was updated successfully, but these errors were encountered: