-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
android: fails to build with "unresolved import linux_raw_sys::ioctl
"
#862
Comments
sylvestre
added a commit
to sylvestre/coreutils
that referenced
this issue
Apr 29, 2023
nextest does build because of: 2023-04-29T08:03:36.5411530Z Compiling log v0.4.17 2023-04-29T08:03:36.5412100Z error[E0432]: unresolved import linux_raw_sys::ioctl 2023-04-29T08:03:36.5412710Z --> /data/data/com.termux/files/home/.cargo/registry/src/github.com-1285ae84e5963aae/rustix-0.37.17/src/backend/libc/io/syscalls.rs:384:24 2023-04-29T08:03:36.5413150Z | 2023-04-29T08:03:36.5413830Z 384 | use linux_raw_sys::ioctl::EXT4_IOC_RESIZE_FS; 2023-04-29T08:03:36.5414380Z | could not find ioctl in linux_raw_sys 2023-04-29T08:03:36.5414590Z 2023-04-29T08:03:36.5414840Z For more information about this error, try rustc --explain E0432. 2023-04-29T08:03:36.5415280Z error: could not compile rustix due to previous error 2023-04-29T08:03:36.5415730Z warning: build failed, waiting for other jobs to finish... nextest-rs/nextest#862
This is fixed in rustix 0.37.18. |
Thanks. Going to release a version with the updated rustix shortly. |
cargo-nextest 0.9.52 just got tagged and will be published within the next 30 minutes once binaries are built. Please test it out and let me know whether it works! |
Impressive turnaround, bravo :) |
I can confirm it works great now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to run
cargo install nextest
on Android, it fails with:Full log can be seen:
https://github.com/uutils/coreutils/actions/runs/4837682994/jobs/8621656415#step:8:1767
The text was updated successfully, but these errors were encountered: