-
Notifications
You must be signed in to change notification settings - Fork 709
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
Build for riscv64gc-unknown-linux-gnu failed. #1419
Comments
We have Rust or C implementations for almost every algorithm, so most things work on every architecture. Unfortunately, there are one or two cases where we don't have an architecture-neutral implementation yet. In the case of RISC-V, because it doesn't have a carry flag at all, we may also need to implement some bignum algorithms differently, since the current C implementations are optimized for having a carry flag presently. |
Anything I can do to help? I'm not very familiar with the codebase, but I think if you point me in the right direction I can possibly figure this out. I have RISC-V hardware that we can use for testing things (but obviously cross-compilation + qemu-user-static works, too). Am hoping to be able to help get ring working because I'd like to be able to build some stuff for RISC-V that depend on it! |
error: failed to run custom build command for Caused by: Below is the Cargo.toml for your reference, [package] See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html[dependencies] Could you please help me with the issue? |
@kirana1996 are you building that on RISC-V, and if so, how? |
@xfbs Yes we are building on riscv64. Created Cargo.toml, Cargo.lock and src/main.rs have test program. In same directory i am trying for ´ćargo run´. |
@xfbs I did a quick hack at https://github.com/amock/ring/commit/3273fc2d17cf118d6bd9f162aeaf963967406fe7 to get this to build on ppc64le. I think you can do something similar to get this to build on riscv64. |
@amock, Actually when running sample ring application depends on Cargo.toml, It downloads the ring to ".cargo/registry/src/github-xxx" path,but but this has no support for riscv64. i want know where it was downloading sources from and which file have look,can please help on this.so we can able to change commit id. |
I'm closing this as a duplicate of #1455, which is more generally about supporting little-endian targets we don't have assembly language code for. |
@kirana1996 I got the same error today on Debian Image 69 in the Starfive VisionFive 2 riscv SBC, I installed https://rustup.rs, the apt-get install build-essential,clang-15-tools, lld-15, llvm 15. Then did:
Here is the error from that:
|
Steps to reproduce. I did this on latested Debian, use a docker container if you don't have it.
I'm able to fix some simple compilation errors in the beginning by adding RISCV to the architectures:
This is all I've gotten to so far.
The text was updated successfully, but these errors were encountered: