Open gboehl opened 3 years ago
Numba 0.53.1 uses LLVM 9 (IIRC), while Julia 1.6 uses LLVM 11. In theory numba is statically linked to LLVM and they should interoperate correctly, but evidently they do not. I tried a lot to make the two work together with no avail.
The only fix that works is reverting to Julia 1.5
(There is also a PR open in numba to update to LLVM 11 for the 0.55 release (due in 4 months, I think), but it won't be using the same minor version as Julia so it's entirely possible they won't work together.)
Thanks a lot for the response, downgrading to Julia 1.5 worked for me.
This seems to be an acceptable workaround, maybe it is a good idea to document it somewhere?
Thanks again.
See also JuliaLang/julia#12644 — I thought Julia had fixed this by using LLVM symbol versioning?
It looks like julia has done all it can to solve this problem, which is really caused by the python side of things. I ran into this problem because I installed numba via conda-forge, but the way conda-forge is building and linking LLVM / llvmlite / numba leads to the segfaults. One way to avoid it is to install numba from the numba channel — as in conda install -c numba llvmlite numba
. They build with static linking, which doesn't trigger this problem. It looks like installing from pip would also work.
Anyway, I don't think PyCall can help with this, so I guess this issue should be closed.
Reviving #220, loading
numba
gives me a segfault:Output:
Running arch linux with Julia version:
with
PyCall
version:Same in Python for
Numba version is 0.53.1. on Python 3.9.5.
A similar issue is opened for pyjulia: https://github.com/JuliaPy/pyjulia/issues/443
Any help is much appreciated!