-
Notifications
You must be signed in to change notification settings - Fork 1.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 mips64-musl ioctl consts to c_int #2078
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (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. |
This arch was overlooked or unspecified in earlier PRs that fixed c_ulong to c_int for ioctl.h consts for musl, see PR rust-lang#289, PR rust-lang#301, or PR rust-lang#1097 for such prior art, however these are still args to fn ioctl on mips64-musl, which is expecting c_ints. Some numbers acquired casts to reflect the fact the data is being used and (so should be written as) an unsized bitfield, even if the value is greater than i32::MAX.
13e6aaf
to
1041547
Compare
@bors r+ |
📌 Commit 1041547 has been approved by |
Fix mips64-musl ioctl consts to c_int This arch was overlooked or unspecified in earlier PRs that fixed c_ulong to c_int for ioctl.h consts for musl, see PR #289, PR #301, or PR #1097 for such prior art, however these are still args to fn ioctl on mips64-musl, which is expecting c_ints. Some numbers acquired casts to reflect the fact the data is being used and (so should be written as) an unsized bitfield, even if the value is greater than i32::MAX. Currently rustc is not building on mips64-linux-musl because of this error.
💔 Test failed - checks-actions |
Build failure on sparc64-linux-gnu and aarch64-linux android, appears spurious but both died around the same point aarch64-linux-android
sparc-unknown-linux-gnu
this PR should only affect mips64 targets though, and neither of those libcs. |
@bors retry |
Fix mips64-musl ioctl consts to c_int This arch was overlooked or unspecified in earlier PRs that fixed c_ulong to c_int for ioctl.h consts for musl, see PR #289, PR #301, or PR #1097 for such prior art, however these are still args to fn ioctl on mips64-musl, which is expecting c_ints. Some numbers acquired casts to reflect the fact the data is being used and (so should be written as) an unsized bitfield, even if the value is greater than i32::MAX. Currently rustc is not building on mips64-linux-musl because of this error.
💔 Test failed - checks-actions |
...similar issues, including failures on Do I have the power? @bors retry |
@workingjubilee: 🔑 Insufficient privileges: not in try users |
darn :^) I'll stop fussing I guess. |
@bors retry |
💔 Test failed - checks-actions |
That's... not really more useful, hm.
|
Just comment out the aarch64-android CI for now, this is too much trouble. |
Noted, it's a EDIT: whoops, misread! |
add268b
to
fcae5a7
Compare
@bors retry |
@bors r+ |
📌 Commit fcae5a7 has been approved by |
Fix mips64-musl ioctl consts to c_int This arch was overlooked or unspecified in earlier PRs that fixed c_ulong to c_int for ioctl.h consts for musl, see PR #289, PR #301, or PR #1097 for such prior art, however these are still args to fn ioctl on mips64-musl, which is expecting c_ints. Some numbers acquired casts to reflect the fact the data is being used and (so should be written as) an unsized bitfield, even if the value is greater than i32::MAX. Currently rustc is not building on mips64-linux-musl because of this error.
(retry doesn't pick up new commits) |
Ahh, thank you! |
💔 Test failed - checks-actions |
04a01d5
to
9807fad
Compare
Looks like it does block on doc generation. It's not obvious to me what changed in the last week to make that fail now, but it appears to be pretty stateful and error-prone. I made some changes to the shell script to fix this. It should error less often in the future. |
@bors r=Amanieu |
📌 Commit 9807fad has been approved by |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13 |
This arch was overlooked or unspecified in earlier PRs that fixed
c_ulong to c_int for ioctl.h consts for musl, see PR #289, PR #301,
or PR #1097 for such prior art, however these are still args to
fn ioctl on mips64-musl, which is expecting c_ints.
Some numbers acquired casts to reflect the fact the data is being
used and (so should be written as) an unsized bitfield, even if
the value is greater than i32::MAX.
Currently rustc is not building on mips64-linux-musl because of this error.