Repository navigation
Conversation
This platform was added to Rust's tier 2-with-tools support list [1] and first shipped in stable Rust in 1.98.0 on 2026-08-20. Rustup gained support for this platform in rust-lang#4908, but with `skip-stable`. I haven't fully internalized all of the CI setup here but my understanding is that this is why a `curl | bash` install on my FreeBSD/aarch64 machine fails with a 404. In rust-lang#4908 it was noted that there could be a second PR once the target stablizes; the PR was in June and pre-dated the stable release of this platform's tier-2 support. This PR thus removes that `skip-stable` flag. It also adds a clause to select an aarch64 VM when running the Rust Docker image, similar to the Linux case. Happy to adjust as needed -- I haven't fully internalized the CI setup here, I'm just following the clues I have found so far. Thanks! [1]: https://doc.rust-lang.org/nightly/rustc/platform-support.html
|
@cfallin Thanks for the patch! Please have a look at our dev guide where I have just added a section dedicated to this task (you should be at step 2 at this point). Please note that the CI files are generated from I'd love to provide any further information that you may need. |
|
I just remembered today that it was probably time to submit a PR for this, fun coincidence! @cfallin feel free to finish this up if you'd like, otherwise I'm happy to do so as well :) |
|
Thanks! I pushed a regen-from-template and then, in a separate commit, a change to run CI here. Unfortunately it seems that there is a problem with the existing Docker container for This is turning into a little more debugging than I had hoped for a drive-by improvement on an issue I noticed; so @mrkajetanp if you know more about the Docker build container here, please feel free to take over! |
This platform was added to Rust's tier 2-with-tools support list 1 and first shipped in stable Rust in 1.98.0 on 2026-08-20.
Rustup gained support for this platform in #4908, but with
skip-stable. I haven't fully internalized all of the CI setup here but my understanding is that this is why acurl https://sh.rustup.rs | bashinstall on my FreeBSD/aarch64 machine fails with a 404.In #4908 it was noted that there could be a second PR once the target stablizes; the PR was in June and pre-dated the stable release of this platform's tier-2 support.
This PR thus removes that
skip-stableflag. It also adds a clause to select an aarch64 VM when running the Rust Docker image, similar to the Linux case.Happy to adjust as needed -- I haven't fully internalized the CI setup here, I'm just following the clues I have found so far. Thanks!