-
Notifications
You must be signed in to change notification settings - Fork 53
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
Intel MKL FATAL ERROR: Cannot load libmkl_intel_thread.2.dylib.
on x86_64 macOS
#281
Comments
so I think my question is still open: how do I choose the MKL used by FFTW? |
What's the output of
in that environment? |
|
Well, MKL_jll 2023.2.0+0 does have the x86_64 Darwin build: https://github.com/JuliaBinaryWrappers/MKL_jll.jl/blob/MKL-v2023.2.0%2B0/src/wrappers/x86_64-apple-darwin.jl, https://github.com/JuliaBinaryWrappers/MKL_jll.jl/blob/596307356acbf1806b77b6c0f7233de501c4bb02/Artifacts.toml#L39-L47 |
how do I query which MKL is being used by fftw? |
using MKL_jll
pkgversion(MKL_jll) |
Also using MKL_jll
MKL_jll.is_available() |
ok, I don't know internals, but I got the impression that fftw installs is own MKL and presumably this is distinct from user installed, because deps run their own versioning. When I install FFTW on its own I don't see an MKL_jll appear in the project. If I install my own MKL_jll I would assume that this is distinct from the one FFTW uses for its own deps, no? |
No: Lines 5 to 9 in ef8fc5b
That seems unlikely since MKL_jll is a direct dependency of this package. How are you checking the project? For example,
No. Why would it be the case? In each environment there can be one and only one version of each package. |
Should fix your problem. |
Fixed. Thanks for your help and explanation! |
Intel MKL FATAL ERROR: Cannot load libmkl_intel_thread.2.dylib.
on x86_64 macOS
#280 was not fixed by installing the 2023 mkl:
The text was updated successfully, but these errors were encountered: