In D33768#763621, @kfv_kfv.io wrote:

Should I necessarily write a patch for Cargo.toml and remove openssl-src-111.17.0+1.1.1m
despite the fact that I have taken care of it in CARGO_FEATURES macro?

• Rebase after Rust 1.57.0 update

@mikael Should we disable the backtrace libunwind backend for armv* like in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259799#c40 or do we leave it on?

In D33190#750726, @evgeniy_khramtsov.org wrote:

To avoid regressing D32654 maybe also apply files/patch-vendor_cc_src_lib.rs to the versioned vendor/cc-1.0.69/src/lib.rs.

• lang/rust: Apply cc crate patch to additional cc-1.0.69 crate too

I've added ports-mgmt/sccache-overlay which comes with a ports overlay with a sccache binary for the host that can also work inside of non-native jails. Everything just works (YMMV) once you enable the overlay and the normal ccache support in Poudriere.

In D32881#747260, @pkubaj wrote:

Why not just add COMPAT_FREEBSD11 to riscv64 kernel? That's what I did for powerpc64le (support added in 13.0) to have Rust working.

• bootstrap.py: Detect riscv64 cputype properly

• Build the riscv64 bootstrap with debug=true for now

• Update riscv64 bootstrap checksums

• Update riscv64 patches based on @jrtc27's work
• Disable backtrace on riscv64 (bug in _Unwind_Backtrace that causes the SIGBUS?)

In D32881#742229, @jrtc27 wrote:

This looks incomplete, I hacked this up a while ago building from upstream sources with P522 P523 P524 P525 (doesn't include the target.rs, didn't git add that, but it's the same as yours)

I mean just use "community supported" then?

Just put "unsupported" after the option description. Let's hope somebody supports it once it's in. Some of the interested committers in here can commit it.

Technical issues aside: Is there a committer who is going to own/support this?