Bootstrapping `psm` is non-trivial

I'm working on bootstrapping a Rust toolchain and psm was a compiled dependency. Due to the amount of binary artifacts included in the vendored Rust tarball, I added a pass to remove all .o, .a, .so, .lib, .dll, and .exe files while also stripping all executable bits. In doing so, I noted psm failed to build due to expecting wasm.o.

Building wasm.o myself was easy enough, the command to do included in the wasm.s file. Unfortunately, my wasm.o differs from the vendored wasm.o, so not only can I not reproduce the wasm.o included in the repository (presumably due to the age of the toolchain it was created with), the Rust build won't continue as the package's digest has changed.

While I can continue the work on patching the build system on my end, just patching the .cargo-checksum.json file (which I have to do for all other crates which also committed binary artifacts, and the Cargo.locks) I'd like to open the issue upstream that psm cannot be bootstrapped/reproduced and request the build.rs build the wasm.o, as done for all other targets. I would guess the decision was made years ago to ship the artifact due to the lack of WASM toolchains laying around, but I'd hope this can be revisited now?

Start with psm's build.rs and the wasm.s file, including the build command documented there. Check how wasm.o is currently supplied and how other targets are built. Done means the build process generates wasm.o instead of relying on the vendored artifact and remains reproducible without requiring a checksum workaround.