旧世界的 Rust crate `linux-raw-sys` 缺少 `general::open_how` 接口？

larch

我尝试在 Loongnix 系统上在 rustix 1.x 分支运行 cargo test, 结果出现如下报错：

error[E0432]: unresolved import linux_raw_sys::general::open_how
--> /home/loongson/.cargo/registry/src/crates.loongnix.cn-7478b521915992e1/rustix-0.38.18/src/backend/libc/fs/syscalls.rs:1674:9
|
1674 | use linux_raw_sys::general::open_how;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no open_how in general
|
help: consider importing one of these items instead
|
1674 | use crate::backend::c::open_how;
| ~~~~~~~~~~~~~~~~~~~~~~
1674 | use libc::open_how;
| ~~~~~~~~~

For more information about this error, try rustc --explain E0432

LMark

larch 之前也遇到过，刚刚看了一下，完全没有修复。版本0.4.10和0.6.0

larch

另外又发现旧世界的 rustup 装不了 nightly 版本，导致有些项目有如下报错：

--- stderr
error: the option Z is only accepted on the nightly compiler

note: selecting a toolchain with +toolchain arguments require a rustup proxy; see https://rust-lang.github.io/rustup/concepts/index.html

help: consider switching to a nightly toolchain: rustup default nightly

note: for more information about Rust's stability policy, see https://doc.rust-lang.org/book/appendix-07-nightly-rust.html#unstable-features

REDEAST

拥抱新世界吧！

larch

刚又发现旧世界装不了 cbindgen 了？报错跟好像也跟 linux_raw_sys 有关:

error[E0425]: cannot find value FS_IOC_GETFLAGS in module c
--> /home/larch/.cargo/registry/src/crates.loongnix.cn-7478b521915992e1/rustix-0.38.30/src/fs/ioctl.rs:142:57
|
142 | let ctl = ioctl::Getter::<ioctl::BadOpcode<{ c::FS_IOC_GETFLAGS }>, u32>::new();
| ^^^^^^^^^^^^^^^
|
::: /home/larch/.cargo/registry/src/crates.loongnix.cn-7478b521915992e1/libc-0.2.152/src/unix/linux_like/linux/mod.rs:2921:1
|
2921 | pub const SIOCGIFFLAGS: ::c_ulong = 0x00008913;
| --------------------------------- similarly named constant SIOCGIFFLAGS defined here
|
help: a constant with a similar name exists
|
142 | let ctl = ioctl::Getter::<ioctl::BadOpcode<{ c::SIOCGIFFLAGS }>, u32>::new();
| ~~~~~~~
help: consider importing this constant
|
5 + use linux_raw_sys::ioctl::FS_IOC_GETFLAGS;
|
help: if you import FS_IOC_GETFLAGS, refer to it directly
|
142 - let ctl = ioctl::Getter::<ioctl::BadOpcode<{ c::FS_IOC_GETFLAGS }>, u32>::new();
142 + let ctl = ioctl::Getter::<ioctl::BadOpcode<{ FS_IOC_GETFLAGS }>, u32>::new();
|
error[E0425]: cannot find value FS_IOC_SETFLAGS in module c
--> /home/larch/.cargo/registry/src/crates.loongnix.cn-7478b521915992e1/rustix-0.38.30/src/fs/ioctl.rs:161:57
|
161 | let ctl = ioctl::Setter::<ioctl::BadOpcode<{ c::FS_IOC_SETFLAGS }>, u32>::new(flags.bits());
| ^^^^^^^^^^^^^^^
|
::: /home/larch/.cargo/registry/src/crates.loongnix.cn-7478b521915992e1/libc-0.2.152/src/unix/linux_like/linux/mod.rs:2922:1
|
2922 | pub const SIOCSIFFLAGS: ::c_ulong = 0x00008914;
| --------------------------------- similarly named constant SIOCSIFFLAGS defined here
|
help: a constant with a similar name exists
|
161 | let ctl = ioctl::Setter::<ioctl::BadOpcode<{ c::SIOCSIFFLAGS }>, u32>::new(flags.bits());
| ~~~~~~~
help: consider importing this constant
|
5 + use linux_raw_sys::ioctl::FS_IOC_SETFLAGS;
|
help: if you import FS_IOC_SETFLAGS, refer to it directly
|
161 - let ctl = ioctl::Setter::<ioctl::BadOpcode<{ c::FS_IOC_SETFLAGS }>, u32>::new(flags.bits());
161 + let ctl = ioctl::Setter::<ioctl::BadOpcode<{ FS_IOC_SETFLAGS }>, u32>::new(flags.bits());

hev

已经修复了

larch

hev 谢谢 👍️ 麻烦再确认下旧世界的 crate target v2.0.0 是不是没有适配？

本站文章除其作者特殊声明外，一律采用CC BY-NC-SA 4.0许可协议进行授权。
进行转载或二次创作时务必以相同协议进行共享，严禁用于商业用途。