Closed aig787 closed 9 months ago
I am also seeing this for what it's worth with cargo-lambda, linked the issue :point_up:
Can you print the output from build.rs with cc v1.0.83, I think it's probably because of the different compiler detection and compiler flags that caused this?
It looks like the newly released cc 1.0.84 crate breaks cross compilation. It's happening to me with a number of crates, but it's reproducible with https://github.com/briansmith/ring.
Running
cargo build
works on a fresh clone (which pulls in1.0.84
), but running zigbuild with a target specified (tested with aarch64-unknown-linux-musl, x86_64-unknown-linux-musl, and aarch64-unknown-linux-gnu) results inIf I pin
=1.0.83
, all targets compile without issues again.