-
Notifications
You must be signed in to change notification settings - Fork 5
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
riscv architecture support? #19
Comments
To clarify with supporting: to build and publish a docker image which can be executed on a riscv system. Current image does not support linux/riscv:
|
Looks like that was a pretty easy addition via #22; I'm going to test with a quick pre-release (that doesn't change the ":latest" tag for mquery) and probably will ask you to verify it since I don't have access to risc-v hardware :) Once we do that, then I can make a non-pre-release and it should work out of the box for risc-v. |
@olof-nord would you mind trying the v0.5.0-rc.0 image to make sure it works? It shows that it should support riscv now:
You should be able to verify on riscv by running:
|
Of course, and I can report success! Many thanks for this, I really appreciate it.
|
Great! I tagged Release: https://github.com/estesp/mquery/releases/tag/v0.5.0 |
I am wondering if this project would like to support the riscv architecture.
RISC-V is an open standard instruction set architecture (ISA) based on established reduced instruction set computer (RISC) principles. Unlike most other ISA designs, the RISC-V ISA is provided under open source licenses that do not require fees to use. (from Wikipedia)
Golang supports cross-compiling risc-v already (GOARCH=riscv64/GOOS=linux), and looking into this project I think adding a new architecture would be quite achievable.
As an early riscv docker user, most if not all docker images does not support riscv yet, and being able to run this tool from a riscv docker system would be great to know what arch is supported and what is not.
The text was updated successfully, but these errors were encountered: