Closed cjpatton closed 3 months ago
My guess is that you have a Cargo.lock
file that's pinning an old version of the cc
crate. Look for a section like this:
[[package]]
name = "cc"
version = ...
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = ...
cc
added the emit_rerun_if_env_changed
method in their v1.0.74. Are you pinning a version older than that? (We started using that method in our v1.5.2, which is why you don't see the build break before that.)
There are a couple of sketchy contributing factors here: We depend on features that are newer than the version of cc
we declare in our Cargo.toml
. I'll fix that now. Also cc
is bumping their patch version when they add new features, when arguably they should be bumping their minor version.
Thanks, I'll take a look.
Our just-released v1.5.4 updates the cc
dependency to v1.1.12, which should force Cargo to update old lockfiles.
This fails on
master
,1.5.3
, and1.5.2
. I'm able to build1.5.1
.I'm new to this code and don't know yet what the build script is doing. In case it helps, I'm on macOS with an M2 processor and have rust 1.80.1.