-
Notifications
You must be signed in to change notification settings - Fork 143
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
feat(arm64): Add support for arm64. #37
Comments
Hi, @RedstoneWizard08! |
Yay! |
Btw I have tried to use binfmt and qemu and emulation with several different methods, and they always end in errors, glitches, or general slowness. What I was talking about for this was more of a native solution that does not have to use emulation. |
That's more of a temporary solution than an actual fix (which we're interested in pursuing) - native ARM support is much better |
Ok, good. |
This did not work for me. It still said something along the lines of "/Linux/ARM64/v8 not found in the manifest list entries" |
Yeah. Binfmt/qemu is a temporary solution. Those arm64 images will be made available when arm64 binary builds are. |
Is there any way for me to selfhost Revolt on an ARM64-based system like a Raspberry Pi in the meantime through emulation or something similar? The command that VevooltPro provided did not fix the issue. |
I tried hosting it on my Raspberry Pi 3.
did my step 2 screw everything up or did an update make this impossible again? |
Edited OP, this should only affect the web client now. Backend has arm64 support across all services. |
This is the issue for a PR I made (#35). There are more details there.
Maintainer edit: this only affects the web client now.
The text was updated successfully, but these errors were encountered: