-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
aarch64 Linux Wheels #220
Comments
Since the last version, we do universal2 builds for macOS which work both on aarch64 and x64 at the same time, which is better in my opinion. The bad thing is Github Actions does not support managed runners yet, only self-hosted ones and we neither have infrastructure nor manpower to host the runner ourselves. So while there are build, they are not tested on aarch64 at all and may stop working at any time. I run tests on my M1 Macbook from time to time, but until there is a hosted option for Github Actions runner, it will not move futher. cf: |
Thanks for the clarification, but I am asking specifically about Linux aarch64, not OSX. I know the managed OSX runners on Github Actions still aren't fully usable with Python, but with Linux they should work - I build aarch64 wheels for mecab-python3 and fugashi. For example here is the action for aarch64 wheels for fugashi. I don't think Linux aarch64 is that common, but it does include Raspberry Pi users, and potentially people running Linux (or Docker) on M1 machines. |
Ah, Linux aarch64. I completely missed Linux in your first post, apologies. Pull request is welcome! Current linux build does PGO which is good for binary builds, but it probably should work on aarch64 as well with minor modifications. |
In my case, I just installed rust :
Then I just did:
as it is instructed, and installed successfully! |
I noticed you don't have wheels for aarch64 for Linux. Do you have any plans to release such wheels?
Github Actions supports this architecture, so it looks like you can probably just make a small change to the current wheel building actions.
The text was updated successfully, but these errors were encountered: