messense

Might needed to add `～/.cargo/bin` to `PATH`, but I'm not sure where to put it in this repository.

We could also install Rust/Cargo in `/usr/local` but then we need to set env var `CARGO_HOME=/usr/local` ```bash curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | CARGO_HOME=/usr/local sh -s -- -y #...

> What about `/usr/local/bin`? The above command will put `cargo` in `/usr/local/bin`, but it also requires setting `CARGO_HOME=/usr/local` for cargo to find it target sysroot etc. Also `RUSTUP_HOME`: https://rust-lang.github.io/rustup/installation/index.html#choosing-where-to-install

On GCC 11.2.0 ``` = note: /usr/local/musl/bin/../lib/gcc/s390x-unknown-linux-musl/11.2.0/../../../../s390x-unknown-linux-musl/bin/ld: /usr/local/musl/bin/../lib/gcc/s390x-unknown-linux-musl/11.2.0/../../../../s390x-unknown-linux-musl/bin/ld: DWARF error: can't find .debug_ranges section. /home/rust/src/target/s390x-unknown-linux-musl/debug/deps/libopenssl_sys-70172c64409e3e90.rlib(curve448.o): in function `recode_wnaf': curve448.c:(.text.recode_wnaf+0xee): undefined reference to `__ctzdi2' /usr/local/musl/bin/../lib/gcc/s390x-unknown-linux-musl/11.2.0/../../../../s390x-unknown-linux-musl/bin/ld: read-only segment has dynamic relocations collect2:...

> What was that other error you got on `aarch64` which forced you to change it back to using GCC 9.2? https://github.com/messense/rust-musl-cross/pull/67#issuecomment-1251905512

bors try amd64 --target powerpc64-unknown-linux-musl

> ABI version 1 is not compatible with ABI version 2 output Looks like gcc is compiled with ELFv1, but Rust uses ELFv2 for powerpc64 musl targets, see https://github.com/rust-lang/rust/issues/60617 (or...

See https://wiki.debian.org/ArmHardFloatPort/VfpComparison#FPU > `VFPv3-D16` is the common denominator of the processors to support here (therefore the recommended build option is `-mfpu=vfpv3-d16`)

rustc uses `vfp3-d32`, perhaps we should use that as well. ``` $ rustc +nightly --print target-spec-json -Zunstable-options --target armv7-unknown-linux-musleabihf { "abi": "eabihf", "arch": "arm", "crt-objects-fallback": "musl", "crt-static-default": true, "crt-static-respected": true,...

> are you able to test it on device(s) that _are_ different? No, I only have a RPi4. I think it might be better to align with whatever rustc defaults...