-
Notifications
You must be signed in to change notification settings - Fork 67
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
Juliacall on Apple M1 #175
Comments
You're using Julia 1.8, which isn't released yet. I'm afraid I don't have time to support dev versions of Julia. If it's still a problem with the released version, please reopen the issue. |
Ahh, right, I was using 1.8 because of random Zygote segfaults with 1.7. Thanks for pointing this out. It works with 1.7. |
Is there a work-around for this? Julia 1.8 (which became a release candidate May 27), is the only available binary for M-series macs so I'm also dealing with this. I'm evaluating whether I could port PySR to PythonCall from PyJulia but need to have it working for M-series. |
JuliaCall works fine with 1.8.0-rc1 on other platforms, so the problem is specific to the M-series. Since that is already an experimental platform for Julia, I don't have the time to support it. But I'm happy to take PRs if you find ways to improve compatibility. |
I'm investigating this issue, The line that crashes is: A minimal example that reproduces the issue: import ctypes
lib = ctypes.CDLL("/Applications/Julia-1.8.app/Contents/Resources/julia/lib/libjulia.1.8.dylib")
lib.jl_init__threading() Any clue? |
@gnuille thanks for posting. What happens to @cjdoris Are you sure that PythonCall works on Julia 1.8-rc1 on other systems? The symbol |
@MilesCranmer it segfaults :( |
yes, it works great in linux with 1.8c-1. Anyway, the same issue occurs when calling jl_init |
Hi, thank you for
PythonCall.jl
/juliacall
! I hope it's ok to just open an issue here.When trying to
import juliacall
on Apple M1 I am getting the following error:I would be really happy about any help with this. Thanks again! :)
The text was updated successfully, but these errors were encountered: