Alexander Huszagh

Related to #639.

Running `cargo clean` fixed this, so it might be a build fingerprint issue or incremental build issue. Either way, not replicating for me anymore.

I'm getting this when I mix the nightly and stable toolchains for a given target. ```bash $ cross run --target armv7-unknown-linux-gnueabihf Finished dev [unoptimized + debuginfo] target(s) in 0.11s Running...

Still not sure, it doesn't reproduce very frequently. I think it's the above, but it should be invalidated and most of the time it is.

I'm getting issue just building `cross` with cargo for when switching between Windows-native and WSL with an identical error message, suggesting to me this isn't cross-specific: ```bash $ cargo build...

This still needs to support the cargo environment variables, which luckily shouldn't be too hard.

This now supports environment variables, and the design is similar to the cross configuration files (and much more logical), but avoids parsing variables except for those we know and lazily...

Temporarily marking as a draft since this might have undergone a bad rebase, and I don't have the time right now to verify that it's correct.

We now pre-ship containers with cross installed, such as `ghcr.io/cross-rs/cross:main`. This might make it a bit simpler. I'll see if I can get port forwarding to work, however.

I think we can do this in https://github.com/cross-rs/cross-toolchains. It shouldn't be too hard to add an `aarch64-unknown-linux-gnu` target with an older glibc using crosstool-ng.