riscv64gc-unknown-linux-gnu support#2313
Conversation
kinnison
left a comment
There was a problem hiding this comment.
Obviously I can't merge while effective-limits isn't released, and with that CI change, but the rest could go in immediately if you wanted to either split the PR up, or simplify it in the short term.
Cargo.toml
Outdated
| download = { path = "download" } | ||
| error-chain = "0.12" | ||
| effective-limits = "0.4" | ||
| effective-limits = { git = "https://github.com/tblah/effective-limits.rs.git", rev = "5fc9ca2fcf7c698d585325d3aad4a8bbe20b4418" } |
There was a problem hiding this comment.
I take it that there needs to be a patch merged and a new release made for this?
01d668f to
2461c93
Compare
|
@tblah regarding your question in infra docker channel. ^ this is not the Rust that you have installed with |
Cargo.toml
Outdated
| download = { path = "download" } | ||
| error-chain = "0.12" | ||
| effective-limits = "0.4" | ||
| effective-limits = { git = "https://github.com/tblah/effective-limits.rs.git", rev = "4873a008d2b441b2d47ce01f62c6f5ec9c157df9" } |
There was a problem hiding this comment.
if bump libc, why not cargo update -p libc and remove this change.
There was a problem hiding this comment.
The libc changes aren't in a released version yet so I think I have to tell cargo to fetch libc master branch instead of a release.
85134e7 to
8ee1957
Compare
|
Thanks @mati865 it seems to work now that it is building using the stable tool-chain. |
|
As discussed on IRC, let's wait for the libc fix and then consider merging everything cleanly instead |
kinnison
left a comment
There was a problem hiding this comment.
We'll need to undo the effective-limits thing and instead update libc and friends when the releases are done. So let's not consider merging before then.
8ee1957 to
3bd9e54
Compare
|
An update on the status of this: The |
|
Fantastic, I imagine @rbtcollins will get to that PR when he has a chance. I think we might be worried about something else with E-L on another issue, so hopefully that could be soon. |
|
Once that's done, if you could also rebase so that we're good in terms of the CI etc, that'd be excellent. |
|
effective-limits stuff has merged, so this should be cleanup-able now |
28340a1 to
3a66beb
Compare
|
Thanks @rbtcollins @kinnison this should be ready for review |
kinnison
left a comment
There was a problem hiding this comment.
Fundamentally good stuff. I'm slightly worried that people might expect a released rustup with the shell script changes, but we can explain it's not there yet, so I'm okay with that change there. But I think we need a skip-stable in the action template, and then we'll need the workflows regenerating (as a separate commit)
kinnison
left a comment
There was a problem hiding this comment.
This is getting very close. Could you please rebase to fold your two CI changes together; and then as a new commit add the result of running sh ci/actions-templates/gen-workflows.sh which will update the contents of the real workflows.
I'm okay if that results in failed CI on the PR for now, but I want to check things are updated properly (and not updated as appropriate for the stable build fr.ex)
skip-stable because we're not going to release this for now
67c2721 to
401800b
Compare
|
@kinnison I've done the rebase. Running |
|
Cool, let's hope your efforts to get riscv-linux to tier two complete soon, so we can consider a rustup release with it :D |
Current status
rustupbuilds on riscv, tests pass*, and rustup can install toolchains for supported host architectures.Tested on Debian using Qemu full system emulation.
To resolve WIP status
riscv64gc-unknown-linux-gnuhost toolchains forrustupon riscv to be useful.riscv64gc-unknown-linux-gnuto run