-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix android SA_* constants #511
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Thanks for the PR! Unfortunately this'll be a breaking change to libc so we'll have to hold off on this for now, but otherwise we can be sure to merge on the next bump! |
@alexcrichton if you have time, could you add a label for all these fixes-that-are-breaking PRs? :-) |
Sure yeah |
@alexcrichton It this really a breaking change? Can we consider it a bug fix instead? Some others PR with type changes were accepted, for example #489, #516, #523, #533. |
@alexcrichton #489 was my bad. Thank you for the clarifications. |
☔ The latest upstream changes (presumably #538) made this pull request unmergeable. Please resolve the merge conflicts. |
So I just looked at sigaction from the android-24 platform in the NDK, and it seems to me that this PR is wrong. In the NDK, both arch-arm and arch-arm64 have
So, as far as I'm aware, this should really be defined as EDIT: Nevermind me. sa_flag is defined as c_uint on 64-bit platforms there https://android.googlesource.com/toolchain/prebuilts/ndk/r13/+/master/platforms/android-24/arch-arm/usr/include/signal.h#84 So sa_flag is c_uint on 64-bit and c_ulong on 32-bit. |
This is necessary because certain flags in libc have different types, generally due to a mistake when adding the flags to the libc. See rust-lang/libc#511 for an example of such a discrepency.
This is necessary because certain flags in libc have different types, generally due to a mistake when adding the flags to the libc. See rust-lang/libc#511 for an example of such a discrepency.
This is necessary because certain flags in libc have different types, generally due to a mistake when adding the flags to the libc. See rust-lang/libc#511 for an example of such a discrepency.
This is necessary because certain flags in libc have different types, generally due to a mistake when adding the flags to the libc. See rust-lang/libc#511 for an example of such a discrepency.
@malbarbo can you rebase this ? We can give this a try to see if anybody is affected by these changes, and if they aren't then just do them. |
Done. |
@bors: r+ |
📌 Commit e2bbeed has been approved by |
Fix android SA_* constants Trying to crosscompile wait-timeout to armv7-linux-androideabi I found that SA_* had different types in libc, but they have to be the same because they are used in bitwise operations.
Fix android SA_* constants Trying to crosscompile wait-timeout to armv7-linux-androideabi I found that SA_* had different types in libc, but they have to be the same because they are used in bitwise operations.
☀️ Test successful - checks-cirrus, checks-travis, status-appveyor |
Trying to crosscompile wait-timeout to armv7-linux-androideabi I found that SA_* had different types in libc, but they have to be the same because they are used in bitwise operations.