-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails with v0.2.11 on crates.io after updating to Clang 16 #75
Comments
Sorry! This is a duplicate of #74. |
Ah so this should be fixed with the dependabot changes in #73? I'll bump the patch version for a publish to crates.io shortly. I tend to be a little hesitant to publish right after a bindgen bump as it's hard to know if generated rust may have breaking changes. |
Hmm, even with this, i still get this error:
I experienced it on Monterey, upgraded to Ventura (13.3) out of curiosity and still see it. I'm not sure what the latest is settings i should use are, but i have the env set to:
Though i'm also using Nix (on Mac, ofc), and trying various things to get it working there with no luck either. Perhaps this should be a new issue. Any thoughts? Note that edit: Hmm, no this looks to be a completely unrelated error? Just lots of path finding errors in this repo, all unique .. hm. Apologies, will open a new issue. |
After updating to Clang (LLVM) 16, building
coreaudio-sys
v0.2.11 from crate.io began to fail with errors like"enum_(unnamed_at_...)" is not a valid Ident
.Here is a detailed log:
This seems to be caused by a change in Clang's behavior mentioned in this fixed issue for the
bindgen
crate, and it is not occurring in themaster
branch ofcoreaudio-sys
because Dependabot updatedbindgen
from v0.61 to v0.64.As a temporary workaround, I have added the following
patch
section to myCargo.toml
, but I believe that once the currentmaster
branch is released on crates.io, it will help prevent unexpected build errors for users of crates that depend on this crate.I hope this is helpful:)
The text was updated successfully, but these errors were encountered: