-
Notifications
You must be signed in to change notification settings - Fork 27
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
Compile/test error on Apple M1 #155
Comments
Hi @JakobAsslaender, I think this issue can be worked on now that all binary dependencies are available on The "easy fix" would be to see if it builds from source locally https://juliaapproximation.github.io/FastTransforms.jl/dev/dev/#The-developer's-right-to-build-from-source-1 and if not report any errors and possibly warnings too. (I don't have an M1 yet, and I don't know if there's any CI that has it, so that might actually speed things up.) |
Thanks, @MikaelSlevinsky for the quick response and the kind support! The error I am getting again related to the BinaryProvider.jl package and the issue #205. Here is the error message:
|
I see. Well, it looks like the only use of BinaryProvider here is to configure the build script, which is technically independent (just a convenience) to checking whether or not the library compiles on a particular platform. |
On my quest of debugging this, I removed BinaryBuilder.jl form the Project file and the build.jl--as well as I could. The latter now looks the following:
Compiling now throws the following error message
Note that I did run Again, thanks a ton for your support! |
Next step: I hacked the makefile (~/.julia/dev/FastTransforms/deps/FastTransforms/Make.inc) -- really not the way to go, I know -- to have the following includes and links instead of the original ones:
With this, FastTransforms compiles! Yet, I still cannot compile Approxjfun.jl, it still throws the following error:
Once again, thanks for your help @MikaelSlevinsky ! |
Ok, that's really great news: thank you for testing this! (A while ago, I made sure that the library compiled on AArch64, but never tested specifically with macOS + AArch64.) This means that the release cycle of a new build with precompiled binaries should be relatively straightforward. Let me take a look over the next week or two. |
I get the same error When trying to run
I get the following error:
Does that help to trace the error, @MikaelSlevinsky ? |
Try moving the library to ~/.julia/dev/FastTransforms/deps/libfasttransforms.dylib |
Thanks! Sorry, the last one was a stupid mistake of mine. I got it to install alright -- and I can use the package. Yet, the test routine throws a segmentation fault:
Again, many thanks for your help! |
@MikaelSlevinsky I am interested in using FastTransforms on an Apple M1 CPU too. I currently get this error while trying to install it:
|
Hi, in principle this would be feasible by a small change to the build script in Julia's Yggdrasil. I'm personally hesitant because
All that said, enthusiastic pull requests from folks with the right tools would not be ignored! |
I sent a PR here that should work on Apple M1 using Julia v1.7: JuliaPackaging/Yggdrasil#4161 |
This is awesome, is it time to get an M1?? (Or maybe wait til M2 at this point) |
Work bought me an M1 pro for Christmas though it won't come in for a couple more weeks. (I didn't want to mention it to falsely get people's hopes up, but yeah this is great progress @abhayap) |
Thanks @MikaelSlevinsky! |
Let's assume this issue is closed now with v0.13.3 on Julia v1.7 |
Hi!
I just quickly wanted to draw your attention to an error I get when trying to install FastTransforms.jl (or ApproxFun.jl) on an Apple M1 CPU natively (Julia v1.7.0-rc1). I know this platform is only Tier-3 and has still many issues, but maybe there is an easy fix for this? The issue seems to be related to BinaryProvider.jl, yet, I am posting this here since BinaryProvider.jl does not seem to maintained based on the last commit being 1.5 years old.
Thanks a ton for looking into this!
The error message when running
test FastTransforms
message is:The text was updated successfully, but these errors were encountered: