stefson

I continued my porting, it was painfree up to rust-1.53.0 which allows to build firefox-96.0 and unbreaks cbindgen, and cargo-c also. With rust-1.54.0, I'm a bit stuck because `compiler/rustc_codegen_ssa/src/back/link.rs` has...

other than that, things are just fine: ``` rustc -Vv rustc 1.58.1 binary: rustc commit-hash: unknown commit-date: unknown host: x86_64-gentoo-linux-musl release: 1.58.1 LLVM version: 13.0.0 ```

Yes I did have a look at them, but for some reason it doesn't ship the libc patch and when I finally got that sorted out I must have forgotten...

hey, I just saw that you forwarded the ebuilds to 1.58.1 and 1.59.0, including the patchset - seems you agree with me to drop the libc patch for 1.59.0 -...

@smaeul I managed to continue with backporting your patchset up to rust-1.64.0, and I also managed to repack all of rustc, rust-std and cargo into one stage: `rust-1.64.0-armv7a-unknown-linux-musleabihf.tar.xz` It would...

Issue with rust-1.65.0_beta was solved via https://github.com/rust-lang/rust/pull/101942

steam overlay has been a source of constant joy and happieness for the longest time, so you may want to disable it?

The build.log itself isn't very usefull, as it hides the actuall compile commands from the user. Therefore, the first thing to do in an attempt to debug this is, to...

next step would be to find out, wether a build outside of portage would work: I copied the folder `src` and `Cargo.toml` from `/var/tmp/portage/dev-util/cbindgen-0.6.7/work/cbindgen-0.6.7/` to temporary folder, entered it via...

one smoking gun I found is, that upon linking during cross-compile cargo has to be told about where the cross-gcc is to be found via ~/.cargo/config `[target.armv7-unknown-linux-gnueabihf] linker = "armv7a-unknown-linux-gnueabihf-gcc"`...