Closed Colerar closed 1 year ago
The immediate workaround for you is to have bindgen
in your $PATH
as the error message indicates.
You can do that right now without any input from this end.
A more fundamental issue is that we rely on the presence of bindgen
on the system. This should probably be fixed to remove dev annoyance.
The immediate workaround for you is to have
bindgen
in your$PATH
as the error message indicates.
Yes, I already have bindgen
in my $PATH
, and the error still occurs:
❯ where bindgen
/Users/col/.cargo/bin/bindgen
❯ bindgen --version
bindgen 0.59.2
Is this a Mac-specific thing perhaps?
I don't have a Mac so don't know why the script would not honor your $PATH
. I would think that it should.
Mentioned also in https://github.com/google/rust_icu/pull/274
A more fundamental issue is that we rely on the presence of
bindgen
on the system. This should probably be fixed to remove dev annoyance.
may be related: https://github.com/rust-lang/cargo/issues/9096
currently it's a unstable feature for cargo.
OK, so this should work in a container (and does on my end!).
Perhaps it could be fixed by referring to the binary's absolute path since the buildenv containers are known and fixed.
This is fixed, and is now guarded by a presubmit check at https://github.com/google/rust_icu/pull/279
To wit, the issue was that make static-bindgen
mounted cargo's bin
directory from the host into the container, and there is a library version mismatch between most hosts and the rust:1.70
container, where the container's required glibc is way newer than that of the host.
This is now fixed, by not mounting the host's cargo bin into the containers when make static-bindgen
runs.