rust-musl-cross VS Musl-LFS

Is my best bet just to use (rust-musl-cross)[https://github.com/messense/rust-musl-cross] as the builder image?

rust-musl-cross: active as last commit was 10 days ago. It said it based on rust-musl-builder. But this repo was created years ago. So why would this exist when there is also rust-musl-builder. What are the differences compared to rust-musl-builder and muslrust?

The example that is provided in the AWS Rust runtime repository shows them using a custom linker and rustup target in order to cross-compile for x86-based lambdas. I attempted to dive into how to get a arm64-based linker, but in the process of trying to figure out how to get that linker installed locally (no convenient packages for Ubuntu, sorry), I stumbled across a project that provides cross-compilation tooling for various platforms via Docker. That made my life a lot easier - Using the rust-musl-cross Docker container, all I have to do is wrap the call to cargo build, and it builds for the proper architecture:

Using Musl instead of Glibc: MLFS

There is an interesting fork of LFS that uses Musl instead of glibc.

https://github.com/dslm4515/Musl-LFS

I played with it for a while as the base OS for my KVM hypervisor servers.

A couple of years ago, I tried to find all the source archives for the old LFS releases. I ended up using the Debian and kernel.org archives to find most of the old package versions. Packages from before 2004 started disappearing like as86 and the PowerPC patches. I was never able to find the PowerPC patches because they were never mirrored on anything but FTP sites. The Internet Archive did not pick up any of those mirrors.