Alexander Huszagh

This still reproduces and doesn't occur with other targets, such as `aarch64-unknown-linux-gnu`. This is odd, since the hosted `CARGO` is native for `x86_64-unknown-linux-gnu`. Even more odd is if we change...

Yep, it is: running on the host produces the following output: ```bash $ wine target/x86_64-pc-windows-gnu/debug/cross-run-cargo.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.10 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact...

I can get it to run using: ```bash >start /unix /rust/bin/cargo --version ``` However, this doesn't give any output.

Partially fixed as of #840, depends on the upstream patch for https://github.com/rust-lang/rust/pull/98216.

This might be somewhat difficult, due to the number of [config options and paths](https://doc.rust-lang.org/cargo/reference/config.html) we'd need to support, ensuring we merge to options. For example: > Cargo allows local configuration...

So the two targets that fail are: - ~~`aarch64-unknown-linux-musl`~~ - `x86_64-unknown-linux-musl` ARM64 musl is actually fine: it just wants to name what it links against as a glibc loader, but...

It shouldn't be too much work, so I think that's fine. We could push it back thought to 0.3.0, since x86_64 Alpine build systems are not too difficult to setup.

It might be worth adding a warning for this target, since it seems to fail with dylib. I might check to ensure it works with static linking C++ dependencies.

Just noticed this in our linked issues, otherwise I would have responded sooner. @krobelus We (as in cross-rs) do actually have a custom Dockerfile to cross-compile from x86_64 to a...

Let me know (or open a discussion on the cross repository) if you have any other interesting toolchains or features you need. Use-cases like this have been super useful to...