-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Installing on Mac M1 #403
Comments
Could you post a larger trace of your REPL like the PastaQ issue commenter? It's not clear what dependency is triggering the error.
Probably not, since the fix there seemed to depend on SCS being an unnecessary dep anyways. That's probably not the case here. In general, FluxML isn't officially making a concerted effort for M1 support at this stage. Though we can do what we can when the fix is clear. |
It's unfortunate Flux does not support M1. More and more people are turning towards them. Wouldn't it be possible to move the dependency that uses BinaryProvider to standard Artifacts? |
I think we need to know which dependency that is first! NNlib itself doesn't do any binary or artifact management, and the direct deps seem simple enough to not immediately arouse suspicion. |
Can confirm that Flux, and NNlib, should work on M1. Flux's tests don't finish, at least on Julia nightly, but haven't investigated why. You probably want 1.8beta or 1.9, not 1.7, though. BinaryProvider doesn't show up as an indirect dependency: https://juliahub.com/ui/Packages/Flux/QdkVy/0.12.9?page=1 . I thought everything stopped using it years ago. Sometimes package conflicts cause you to get a truly ancient version of some package. Can you post |
So this is my environment: (@v1.7) pkg> st
Status `~/.julia/environments/v1.7/Project.toml`
[6e4b80f9] BenchmarkTools v1.3.1
[98e50ef6] JuliaFormatter v0.22.7
[438e738f] PyCall v1.93.1
[6aa20fa7] TensorOperations v2.0.1 I tried installing |
I'm trying to install the library using Julia 1.7 with an arm64 arch in a Mac M1. However, I get the following error:
This looks to be an error triggered by
BinaryProvider
as explained here. Latest release was on 2020 before the Mac M1 was released. Apparently the guys from PastaQ reported the same installation issue, but it looks like they were able to find a fix with this PR.I'm wondering whether a similar fix can be included here. Thanks!
The text was updated successfully, but these errors were encountered: