Lann

@vdice if you get the chance could you check this out?

Thanks!

I predict this is going to be a problem very soon after open sourcing.

We can't make any backward-incompatible changes to an interface (including things as simple as reordering struct fields I think) without running into this right?

Yeah, I think this plays into a larger theme of stability guarantees. We should be explicit about how (un)stable these interfaces are.

@vdice

I spent a little time looking into this today, but even with the above openssl vendoring and using [`cross`](https://github.com/cross-rs/cross) I hit some pretty nasty-looking bugs cross-compiling `wasmtime-fiber`. I would be...

No update yet. Currently the release builds are really more geared toward development environments where ARM Linux is less common. That said, this is mostly blocked on finding a good...

```console $ cargo build --release --target aarch64-unknown-linux-gnu --features openssl/vendored [...many copies of line below...] /usr/bin/ld: /spin/target/aarch64-unknown-linux-gnu/release/deps/spin-50cb93f1b1f7d4bc.spin.d8cbf558-cgu.0.rcgu.o: Relocations in generic ELF (EM: 183) /usr/bin/ld: /spin/target/aarch64-unknown-linux-gnu/release/deps/spin-50cb93f1b1f7d4bc.spin.d8cbf558-cgu.0.rcgu.o: error adding symbols: file in wrong...

This looks promising: https://crates.io/crates/serde_alias