-
Notifications
You must be signed in to change notification settings - Fork 27
Switch to BinaryBuilder.jl #170
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
Comments
FastTransforms.jl has FastTransforms_jll.jl with binaries for M1 Macs. The BinaryProvider route is only for developer support to allow compiling from source. Maybe it's that the build script always gets invoked and it sees that it's |
That's possible. I am not sure how the underlying mechanisms work, but if I try to run tests on an M1 Mac that have FastTransforms as a dependency, this error is invoked. Is there any way that the |
Tagging a new minor release based on this 4bbefc9. Probably will work for you, but let me know if it doesn't. |
This ought to do it ee31e98. |
Great, thanks! I can confirm that with v0.13.9, FastTransforms.jl works on the M1. Kudos for the fast response & fix! |
I can only second that - thank you very much! |
Would you consider switching to BinaryBuilder.jl? We experienced problems with new Apple M1 devices due to the build script of FastTransforms.jl, see trixi-framework/Trixi.jl#1104 (comment)
CC @sloede
The text was updated successfully, but these errors were encountered: