Open palday opened 1 year ago
What's the output of the conda add mne
line? I'm wondering if it's installing an incompatible version of libllvm.
Here's the conda resolution
I had also suspected something with libllvm and it's actually installing two different versions:
+ libllvm14 14.0.6 hd1a9a77_3 conda-forge/osx-arm64 21MB
+ libllvm15 15.0.7 h62b9111_1 conda-forge/osx-arm64 22MB
There seems to be a related but distinct problem when doing this on MacOS on Intel, xref https://discourse.julialang.org/t/using-pymne-crashes-julia/101799
Same version of libllvm14 as Julia.
Maybe the presence of libllvm15 as well causes issues. Why does that get installed?
Or maybe libcxx is incompatible with Julia. What is the result of Base.BinaryPlatforms.detect_libstdcxx_version()
?
Or maybe libcxx is incompatible with Julia. What is the result of
Base.BinaryPlatforms.detect_libstdcxx_version()
?
nothing
Since we've had a few Julia patch releases in the meantime, I also tried this on 1.9.2 and 1.10-beta1 and have the same problem.
I wonder if this is related:
Affects: PythonCall
Describe the bug On M1, I can reliably induce a segfault when loading the Python package
mne
via PythonCall.Your system Please provide detailed information about your system:
Additional context
.CondaPkg/env
) and importing MNE directly does not cause a segfault.I think there's some weird interaction between the Conda build, LLVM dylib and PythonCall.