On Thu, Jan 18, 2024 at 4:49 PM Conor Dooley <conor@xxxxxxxxxx> wrote: > > The bit that worries me most is bindgen, and in particular detecting the > version of libclang used. I mentioned to Nathan or Nick about needing a > buildtime test for the version of LIBCLANG being used. > I'm less worried about this for LLVM=1 builds, since while I think it is > possible to provide a LIBCLANG path to the build system, I suspect that > for LLVM=1 builds it's almost always going to match the LLVM toolchain > in use. `scripts/rust_is_available.sh` tests whether `libclang` is at least the minimum LLVM supported version; and under `LLVM=1` builds, it also tests whether the `bindgen` found one matches the C compiler. Do you mean something like that? For `bindgen` under GCC builds, we will eventually want a "proper" way to use GCC instead (or possibly other approaches like querying the information): https://github.com/rust-lang/rust-bindgen/issues/1949. Recently, there has been a thread in our Zulip and a couple people are experimenting: https://rust-for-linux.zulipchat.com/#narrow/stream/288089-General/topic/Bindgen.20--.20GCC.20backend.20port > I'll do another rebase and resend after the merge window closes I > suppose :) Thanks! Cheers, Miguel
