Closed AshtonSBradley closed 10 months ago
so I think my question is still open: how do I choose the MKL used by FFTW?
What's the output of
]st -m MKL_jll
in that environment?
(@v1.10) pkg> st -m MKL_jll
Status `~/.julia/environments/v1.10/Manifest.toml`
⌅ [856f044c] MKL_jll v2023.2.0+0
Info Packages marked with ⌅ have new versions available but compatibility constraints restrict them from upgrading. To see why use `status --outdated -m`
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?
but I got the impression that fftw installs is own MKL
I install FFTW on its own I don't see an MKL_jll appear in the project.
That seems unlikely since MKL_jll is a direct dependency of this package. How are you checking the project? For example, ]st
only shows the the packages you installed directly, but if you want to see also the other packages pulled by your packages you have to use ]st -m
, as suggested above.
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. Why would it be the case? In each environment there can be one and only one version of each package.
]add IntelOpenMP_jll@2023
Should fix your problem.
]add IntelOpenMP_jll@2023
Should fix your problem.
Fixed. Thanks for your help and explanation!
280 was not fixed by installing the 2023 mkl: