We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Continuing the discussion from #699.
Summary of symptoms:
musl
Basically, it's all fun and games while we're adding constants (#define). But when we need to expose a function from libc.so - we're doomed.
#define
I suggested generating the bindings based on what's already installed on the system (e.g. with rust-bindgen)
rust-bindgen
The text was updated successfully, but these errors were encountered:
Port rust-lang#672 and rust-lang#686 to Android.
52348fe
I'd rather avoid the duplication, this is discussed in rust-lang#707.
20591a3
Auto merge of #710 - marmistrz:android, r=alexcrichton
ecd468e
Port #672 and #686 to Android. I'd rather avoid the duplication, but this is discussed in #707.
Duplicate of #423 .
Sorry, something went wrong.
No branches or pull requests
Continuing the discussion from #699.
Summary of symptoms:
musl
in CI cannot be upgraded since an address family was added, on newer glibc tests fail either (issue AF_MAX/PF_MAX incorrect on local system #665)Basically, it's all fun and games while we're adding constants (
#define
). But when we need to expose a function from libc.so - we're doomed.I suggested generating the bindings based on what's already installed on the system (e.g. with
rust-bindgen
)The text was updated successfully, but these errors were encountered: