Closed cpu closed 3 months ago
I think I figured out the issue. I'll revert this pinning + land a fix once I've gotten a better sense of whether the upstream change was intentional or not (and perhaps if there's a way we could make this test rig less brittle).
Sorry for the noise, try to set CARGOFLAGS=--libdir=lib
it should return to the original behaviour
The recent 0.10.0 release seems to be causing a regression. Until we've had a chance to dig into the root cause let's pin the version in-use in CI to keep the build passing.
I also snuck in an update to print the pkg-config version in-use. I was interested in that data when I wasn't sure if it was the cargo-c update that changed things or if there was an unrelated system image update that bork'd it.