-
Notifications
You must be signed in to change notification settings - Fork 893
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
RISC-V support? #2296
Comments
One could investigate and add risv cpu type to Lines 228 to 296 in c022b92
|
Hmm, tried the obvious
but assuming this follows the convention, the failure is
|
What is the full target triple of riscv? |
Does riscv has std? rustup depends on std. |
|
Changing the
|
There are multiple things at play here.
If people are serious about assisting with this, then perhaps we might put together a checklist and get it underway; though without support from the main |
Thanks, it was exactly a list like this I was hoping to see. Without a published toolchain there's not much point to the rest. IIUC, this is tracked by rust-lang/rust#62117 which I updated to point back here. |
I have a WIP PR for this #2313 It isn't useful yet because there aren't official toolchains for a riscv host. However cross-compilation toolchains can be downloaded for a riscv target today (tested using rustup 1.21.1): see cross-rs/cross#413 |
The completed riscvgc support was released today. I'd be interested to know if it works for you or not. |
Thanks! The script seems to progress on my (fully up-to-date) Ubuntu RISC-V VM. However, it looks like we aren't there yet:
riscv64gc-unknown-linux-gnu is listed under Tier 2 (does that imply not-stable?). |
Taking option 2 and picking nightly didn't help:
|
Okay so we're closer but still no cigar. @tblah Is this what you'd expect for now? |
Rustup for RISC-V won't work until rust-lang/rust#72973 is merged. |
Thanks for that @mati865 |
@tommythorn currently RISC-V is Tier 2 only for cross compilation. But as @mati865 said that may soon change to full support. rust-lang/rust#72973 is waiting for rust-lang/compiler-team#312 to be approved. If there are no objections that could happen about 2 days from now. After that |
@tblah By 'need changing' do you mean for the CI, or a point release being needed to use it? |
@kinnison just CI if I understand correctly. rust-lang/rust#72973 moves the RISC-V build to a new docker image so rustup needs to use that image too here |
I'll make sure to be subscribed to that PR then, though I hope one of the contributors here might get to PRing our CI before me :D |
I'm afraid I lost track of where this is at. I can see that rust-lang/rust#72973 was merged, rust-lang/compiler-team#312 was closed, and Launching rustup.sh (from https://sh.rustup.rs) in a Fedora RISC-V QEMU image leads to
I wasn't immediately able to find out where rustup-init was reading (the manifest? from whence?) and not finding it. |
If it is host toolchain, we have to have riscv build for rustup, then wait until next rustup release. |
I apologize for my ignorance. I poked around some more and discovered that there are indeed nightly builds for RISC-V and lo and behold |
Ok, no objections. Closing. |
Describe the problem you are trying to solve
rustup is wonderful, so it's sad it doesn't support RISC-V, I get "rustup: unknown CPU type: riscv64" which run on Ubuntu 20.04 (which has rustc, cargo, etc).
Describe the solution you'd like
I'd like it to install the latest Rust
Notes
I used the Ubuntu image from https://github.com/carlosedp/riscv-bringup to issue the commands. I assume this is actually blocked on something on rust side, but I didn't see any issues tracking this.
The text was updated successfully, but these errors were encountered: