Issue using `async_trait` with `zigbuild` for x86_64-unknown-linux-gnu about cargo-zigbuild HOT 4 CLOSED

So this issue is caused by Cargo using the same linker when --target is the same as the host target, for more information see rust-lang/cargo#3349 and there is already an unstable option target-applies-to-host to fix it. But you need to use the nightly Rust compiler because that feature is unstable.

First create the .cargo/config.toml file and add target-applies-to-host = false to its content, then run cargo zigbuild with the unstable option enabled:

cargo +nightly zigbuild --target x86_64-unknown-linux-gnu -Ztarget-applies-to-host

from cargo-zigbuild.

With #9 which is released in v0.5.2, the only workaround is switching to nightly Rust, cargo-zigbuild will take care of enabling the target-applies-to-host option automatically.

from cargo-zigbuild.

With commit 407e2e4, if you don't specify a glibc version it'll skip setting up zig as linker and just use system linker instead when the cross target is exactly the same as the host target. That should avoid having to use the target-applies-to-host option most of the time.

from cargo-zigbuild.

I can reproduce this issue on Ubuntu 20.04, but it seems to work fine on macOS.

from cargo-zigbuild.