[INFO] fetching crate libcryptsetup-rs 0.10.0... [INFO] checking libcryptsetup-rs-0.10.0 against try#ccf408f4326a858c00dd845a64a86b16f360a801 for pr-129466-2 [INFO] extracting crate libcryptsetup-rs 0.10.0 into /workspace/builds/worker-0-tc2/source [INFO] validating manifest of crates.io crate libcryptsetup-rs 0.10.0 on toolchain ccf408f4326a858c00dd845a64a86b16f360a801 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate libcryptsetup-rs 0.10.0 [INFO] finished tweaking crates.io crate libcryptsetup-rs 0.10.0 [INFO] tweaked toml for crates.io crate libcryptsetup-rs 0.10.0 written to /workspace/builds/worker-0-tc2/source/Cargo.toml [INFO] crate crates.io crate libcryptsetup-rs 0.10.0 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] a07ae0b07d1da187e17ec74f4b13e47f08fad73567e5d929c57d61b79c80159f [INFO] running `Command { std: "docker" "start" "-a" "a07ae0b07d1da187e17ec74f4b13e47f08fad73567e5d929c57d61b79c80159f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a07ae0b07d1da187e17ec74f4b13e47f08fad73567e5d929c57d61b79c80159f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a07ae0b07d1da187e17ec74f4b13e47f08fad73567e5d929c57d61b79c80159f", kill_on_drop: false }` [INFO] [stdout] a07ae0b07d1da187e17ec74f4b13e47f08fad73567e5d929c57d61b79c80159f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] a13a57950d206fd14a4d74461537afed61c7ccfebbfbf2c01efcf6a59163b137 [INFO] running `Command { std: "docker" "start" "-a" "a13a57950d206fd14a4d74461537afed61c7ccfebbfbf2c01efcf6a59163b137", kill_on_drop: false }` [INFO] [stderr] Copying to /tmp/fixit [INFO] [stderr] Running `cargo fix --edition` [INFO] [stderr] Migrating Cargo.toml from 2021 edition to 2024 [INFO] [stderr] Compiling proc-macro2 v1.0.86 [INFO] [stderr] Compiling glob v0.3.1 [INFO] [stderr] Compiling libc v0.2.155 [INFO] [stderr] Compiling unicode-ident v1.0.12 [INFO] [stderr] Compiling minimal-lexical v0.2.1 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling regex-syntax v0.8.4 [INFO] [stderr] Compiling either v1.13.0 [INFO] [stderr] Compiling bindgen v0.69.4 [INFO] [stderr] Compiling rustc-hash v1.1.0 [INFO] [stderr] Compiling bitflags v2.6.0 [INFO] [stderr] Compiling lazy_static v1.5.0 [INFO] [stderr] Compiling lazycell v1.3.0 [INFO] [stderr] Compiling shlex v1.3.0 [INFO] [stderr] Compiling libloading v0.8.4 [INFO] [stderr] Compiling semver v1.0.23 [INFO] [stderr] Compiling pkg-config v0.3.30 [INFO] [stderr] Compiling itertools v0.12.1 [INFO] [stderr] Compiling serde v1.0.204 [INFO] [stderr] Compiling cc v1.1.5 [INFO] [stderr] Compiling cfg_aliases v0.2.1 [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Checking log v0.4.22 [INFO] [stderr] Checking utf8parse v0.2.2 [INFO] [stderr] Checking anstyle-parse v0.2.4 [INFO] [stderr] Compiling nix v0.29.0 [INFO] [stderr] Compiling clang-sys v1.8.1 [INFO] [stderr] Checking ppv-lite86 v0.2.17 [INFO] [stderr] Compiling nom v7.1.3 [INFO] [stderr] Checking aho-corasick v1.1.3 [INFO] [stderr] Compiling quote v1.0.36 [INFO] [stderr] Checking itoa v1.0.11 [INFO] [stderr] Compiling libcryptsetup-rs v0.10.0 (/tmp/fixit) [INFO] [stderr] Checking is_terminal_polyfill v1.70.0 [INFO] [stderr] Migrating build.rs from 2021 edition to 2024 [INFO] [stderr] Checking anstyle-query v1.1.0 [INFO] [stderr] Compiling syn v2.0.71 [INFO] [stderr] Checking colorchoice v1.0.1 [INFO] [stderr] Checking anstyle v1.0.7 [INFO] [stderr] Checking ryu v1.0.18 [INFO] [stderr] Checking once_cell v1.19.0 [INFO] [stderr] Checking humantime v2.1.0 [INFO] [stderr] Checking anstream v0.6.14 [INFO] [stderr] Checking base64 v0.21.7 [INFO] [stderr] Compiling regex-automata v0.4.7 [INFO] [stderr] Checking getrandom v0.2.15 [INFO] [stderr] Checking errno v0.3.9 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Checking uuid v1.10.0 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Compiling cexpr v0.6.0 [INFO] [stderr] Compiling regex v1.10.5 [INFO] [stderr] Checking env_filter v0.1.0 [INFO] [stderr] Checking env_logger v0.11.3 [INFO] [stderr] Compiling libcryptsetup-rs-sys v0.4.0 [INFO] [stderr] Compiling loopdev-3 v0.5.1 [INFO] [stderr] Migrating src/lib.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `libcryptsetup_rs` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/consts/flags.rs [INFO] [stderr] * src/lib.rs [INFO] [stderr] * src/luks2/reencrypt.rs [INFO] [stderr] * src/macros.rs [INFO] [stderr] * src/mem.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:9:7 [INFO] [stderr] | [INFO] [stderr] 9 | ( $libcryptsetup_call:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:25:7 [INFO] [stderr] | [INFO] [stderr] 25 | ( $rc:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:40:7 [INFO] [stderr] | [INFO] [stderr] 40 | ( $rc:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:54:7 [INFO] [stderr] | [INFO] [stderr] 54 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:61:7 [INFO] [stderr] | [INFO] [stderr] 61 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:68:7 [INFO] [stderr] | [INFO] [stderr] 68 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:80:7 [INFO] [stderr] | [INFO] [stderr] 80 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:88:7 [INFO] [stderr] | [INFO] [stderr] 88 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:95:7 [INFO] [stderr] | [INFO] [stderr] 95 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:103:7 [INFO] [stderr] | [INFO] [stderr] 103 | ( $path:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:117:7 [INFO] [stderr] | [INFO] [stderr] 117 | ( $str:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:127:7 [INFO] [stderr] | [INFO] [stderr] 127 | ( $bytes:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:134:7 [INFO] [stderr] | [INFO] [stderr] 134 | ( $bytes:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:142:7 [INFO] [stderr] | [INFO] [stderr] 142 | ( $str_ptr:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:151:7 [INFO] [stderr] | [INFO] [stderr] 151 | ( $str_ptr:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:161:72 [INFO] [stderr] | [INFO] [stderr] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr_2021 ),* ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/mem.rs:13:77 [INFO] [stderr] | [INFO] [stderr] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr_2021)?) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/lib.rs:45:7 [INFO] [stderr] | [INFO] [stderr] 45 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/consts/flags.rs:31:15 [INFO] [stderr] | [INFO] [stderr] 31 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:33:15 [INFO] [stderr] | [INFO] [stderr] 33 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:35:15 [INFO] [stderr] | [INFO] [stderr] 35 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:37:15 [INFO] [stderr] | [INFO] [stderr] 37 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:39:15 [INFO] [stderr] | [INFO] [stderr] 39 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/luks2/reencrypt.rs:193:11 [INFO] [stderr] | [INFO] [stderr] 193 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:9:7 [INFO] [stderr] | [INFO] [stderr] 9 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:68:7 [INFO] [stderr] | [INFO] [stderr] 68 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:102:7 [INFO] [stderr] | [INFO] [stderr] 102 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:121:7 [INFO] [stderr] | [INFO] [stderr] 121 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:153:17 [INFO] [stderr] | [INFO] [stderr] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:15:15 [INFO] [stderr] | [INFO] [stderr] 15 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:18:15 [INFO] [stderr] | [INFO] [stderr] 18 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:26:15 [INFO] [stderr] | [INFO] [stderr] 26 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 101 | memzero!(SafeOwnedMemZero); [INFO] [stderr] | -------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:15:15 [INFO] [stderr] | [INFO] [stderr] 15 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:18:15 [INFO] [stderr] | [INFO] [stderr] 18 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:26:15 [INFO] [stderr] | [INFO] [stderr] 26 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stderr] | ----------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 150 | memzero!(SafeMemHandle); [INFO] [stderr] | ----------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:134:11 [INFO] [stderr] | [INFO] [stderr] 134 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] error: aborting due to 17 previous errors; 23 warnings emitted [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0658`. [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/lib.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:9:27 [INFO] [stdout] | [INFO] [stdout] 9 | ( $libcryptsetup_call:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 9 | ( $libcryptsetup_call:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:25:11 [INFO] [stdout] | [INFO] [stdout] 25 | ( $rc:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 25 | ( $rc:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:40:11 [INFO] [stdout] | [INFO] [stdout] 40 | ( $rc:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 40 | ( $rc:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:54:11 [INFO] [stdout] | [INFO] [stdout] 54 | ( $rc:expr, $type:ty ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 54 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:61:11 [INFO] [stdout] | [INFO] [stdout] 61 | ( $rc:expr, $type:ty ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 61 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:68:12 [INFO] [stdout] | [INFO] [stdout] 68 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 68 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:80:12 [INFO] [stdout] | [INFO] [stdout] 80 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 80 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:88:12 [INFO] [stdout] | [INFO] [stdout] 88 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 88 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:95:12 [INFO] [stdout] | [INFO] [stdout] 95 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 95 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:103:13 [INFO] [stdout] | [INFO] [stdout] 103 | ( $path:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 103 | ( $path:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:117:12 [INFO] [stdout] | [INFO] [stdout] 117 | ( $str:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 117 | ( $str:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:127:14 [INFO] [stdout] | [INFO] [stdout] 127 | ( $bytes:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 127 | ( $bytes:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:134:14 [INFO] [stdout] | [INFO] [stdout] 134 | ( $bytes:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 134 | ( $bytes:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:142:16 [INFO] [stdout] | [INFO] [stdout] 142 | ( $str_ptr:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 142 | ( $str_ptr:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:151:16 [INFO] [stdout] | [INFO] [stdout] 151 | ( $str_ptr:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 151 | ( $str_ptr:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:161:82 [INFO] [stdout] | [INFO] [stdout] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr ),* ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr_2021 ),* ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/consts/flags.rs:31:15 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:33:15 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:35:15 [INFO] [stdout] | [INFO] [stdout] 35 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:37:15 [INFO] [stdout] | [INFO] [stdout] 37 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:39:15 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/luks2/reencrypt.rs:193:11 [INFO] [stdout] | [INFO] [stdout] 193 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:9:7 [INFO] [stdout] | [INFO] [stdout] 9 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:68:7 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:102:7 [INFO] [stdout] | [INFO] [stdout] 102 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:121:7 [INFO] [stdout] | [INFO] [stdout] 121 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 101 | memzero!(SafeOwnedMemZero); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 150 | memzero!(SafeMemHandle); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/mem.rs:13:83 [INFO] [stdout] | [INFO] [stdout] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr)?) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr_2021)?) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:134:11 [INFO] [stdout] | [INFO] [stdout] 134 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 40 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating examples/unlock-luks2-with-token.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `libcryptsetup_rs` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/consts/flags.rs [INFO] [stderr] * src/lib.rs [INFO] [stderr] * src/luks2/reencrypt.rs [INFO] [stderr] * src/macros.rs [INFO] [stderr] * src/mem.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:9:7 [INFO] [stderr] | [INFO] [stderr] 9 | ( $libcryptsetup_call:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:25:7 [INFO] [stderr] | [INFO] [stderr] 25 | ( $rc:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:40:7 [INFO] [stderr] | [INFO] [stderr] 40 | ( $rc:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:54:7 [INFO] [stderr] | [INFO] [stderr] 54 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:61:7 [INFO] [stderr] | [INFO] [stderr] 61 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:68:7 [INFO] [stderr] | [INFO] [stderr] 68 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:80:7 [INFO] [stderr] | [INFO] [stderr] 80 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:88:7 [INFO] [stderr] | [INFO] [stderr] 88 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:95:7 [INFO] [stderr] | [INFO] [stderr] 95 | ( $ptr:expr_2021 ) => {{ [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:103:7 [INFO] [stderr] | [INFO] [stderr] 103 | ( $path:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:117:7 [INFO] [stderr] | [INFO] [stderr] 117 | ( $str:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:127:7 [INFO] [stderr] | [INFO] [stderr] 127 | ( $bytes:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:134:7 [INFO] [stderr] | [INFO] [stderr] 134 | ( $bytes:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:142:7 [INFO] [stderr] | [INFO] [stderr] 142 | ( $str_ptr:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:151:7 [INFO] [stderr] | [INFO] [stderr] 151 | ( $str_ptr:expr_2021 ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/macros.rs:161:72 [INFO] [stderr] | [INFO] [stderr] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr_2021 ),* ) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/mem.rs:13:77 [INFO] [stderr] | [INFO] [stderr] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr_2021)?) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/lib.rs:45:7 [INFO] [stderr] | [INFO] [stderr] 45 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/consts/flags.rs:31:15 [INFO] [stderr] | [INFO] [stderr] 31 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:33:15 [INFO] [stderr] | [INFO] [stderr] 33 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:35:15 [INFO] [stderr] | [INFO] [stderr] 35 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:37:15 [INFO] [stderr] | [INFO] [stderr] 37 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:39:15 [INFO] [stderr] | [INFO] [stderr] 39 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/consts/flags.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stderr] --> src/luks2/reencrypt.rs:193:11 [INFO] [stderr] | [INFO] [stderr] 193 | #[cfg(cryptsetup24supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:9:7 [INFO] [stderr] | [INFO] [stderr] 9 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:68:7 [INFO] [stderr] | [INFO] [stderr] 68 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:102:7 [INFO] [stderr] | [INFO] [stderr] 102 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:121:7 [INFO] [stderr] | [INFO] [stderr] 121 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:153:17 [INFO] [stderr] | [INFO] [stderr] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:15:15 [INFO] [stderr] | [INFO] [stderr] 15 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:18:15 [INFO] [stderr] | [INFO] [stderr] 18 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:26:15 [INFO] [stderr] | [INFO] [stderr] 26 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 75 | / define_handle! { [INFO] [stderr] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stderr] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stderr] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stderr] ... | [INFO] [stderr] 99 | | } [INFO] [stderr] 100 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 101 | memzero!(SafeOwnedMemZero); [INFO] [stderr] | -------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:15:15 [INFO] [stderr] | [INFO] [stderr] 15 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:18:15 [INFO] [stderr] | [INFO] [stderr] 18 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:26:15 [INFO] [stderr] | [INFO] [stderr] 26 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | / define_handle! { [INFO] [stderr] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stderr] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stderr] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stderr] ... | [INFO] [stderr] 118 | | from_ptr [INFO] [stderr] 119 | | } [INFO] [stderr] | |_- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stderr] | ----------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:41:15 [INFO] [stderr] | [INFO] [stderr] 41 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 150 | memzero!(SafeMemHandle); [INFO] [stderr] | ----------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stderr] --> src/mem.rs:134:11 [INFO] [stderr] | [INFO] [stderr] 134 | #[cfg(cryptsetup23supported)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] error: aborting due to 17 previous errors; 23 warnings emitted [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0658`. [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/lib.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:9:27 [INFO] [stdout] | [INFO] [stdout] 9 | ( $libcryptsetup_call:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 9 | ( $libcryptsetup_call:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:25:11 [INFO] [stdout] | [INFO] [stdout] 25 | ( $rc:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 25 | ( $rc:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:40:11 [INFO] [stdout] | [INFO] [stdout] 40 | ( $rc:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 40 | ( $rc:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:54:11 [INFO] [stdout] | [INFO] [stdout] 54 | ( $rc:expr, $type:ty ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 54 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:61:11 [INFO] [stdout] | [INFO] [stdout] 61 | ( $rc:expr, $type:ty ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 61 | ( $rc:expr_2021, $type:ty ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:68:12 [INFO] [stdout] | [INFO] [stdout] 68 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 68 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:80:12 [INFO] [stdout] | [INFO] [stdout] 80 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 80 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:88:12 [INFO] [stdout] | [INFO] [stdout] 88 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 88 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:95:12 [INFO] [stdout] | [INFO] [stdout] 95 | ( $ptr:expr ) => {{ [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 95 | ( $ptr:expr_2021 ) => {{ [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:103:13 [INFO] [stdout] | [INFO] [stdout] 103 | ( $path:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 103 | ( $path:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:117:12 [INFO] [stdout] | [INFO] [stdout] 117 | ( $str:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 117 | ( $str:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:127:14 [INFO] [stdout] | [INFO] [stdout] 127 | ( $bytes:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 127 | ( $bytes:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:134:14 [INFO] [stdout] | [INFO] [stdout] 134 | ( $bytes:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 134 | ( $bytes:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:142:16 [INFO] [stdout] | [INFO] [stdout] 142 | ( $str_ptr:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 142 | ( $str_ptr:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:151:16 [INFO] [stdout] | [INFO] [stdout] 151 | ( $str_ptr:expr ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 151 | ( $str_ptr:expr_2021 ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/macros.rs:161:82 [INFO] [stdout] | [INFO] [stdout] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr ),* ) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 161 | ( #[$meta:meta] $flag_enum:ident, $flag_type:ty, $( $name:ident => $constant:expr_2021 ),* ) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/consts/flags.rs:31:15 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:33:15 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:35:15 [INFO] [stdout] | [INFO] [stdout] 35 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:37:15 [INFO] [stdout] | [INFO] [stdout] 37 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:39:15 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/luks2/reencrypt.rs:193:11 [INFO] [stdout] | [INFO] [stdout] 193 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:9:7 [INFO] [stdout] | [INFO] [stdout] 9 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:68:7 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:102:7 [INFO] [stdout] | [INFO] [stdout] 102 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:121:7 [INFO] [stdout] | [INFO] [stdout] 121 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 101 | memzero!(SafeOwnedMemZero); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 150 | memzero!(SafeMemHandle); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/mem.rs:13:83 [INFO] [stdout] | [INFO] [stdout] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr)?) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 13 | ($(#[$docs:meta])* $name:ident, $(#[$from_ptr_docs:meta])* from_ptr $(, $drop:expr_2021)?) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:134:11 [INFO] [stdout] | [INFO] [stdout] 134 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:31:9 [INFO] [stdout] | [INFO] [stdout] 31 | std::env::remove_var("FORMAT_WITH_ZEROS"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] = note: `--force-warn deprecated-safe-2024` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 31 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 32 ~ unsafe { std::env::remove_var("FORMAT_WITH_ZEROS") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:33:9 [INFO] [stdout] | [INFO] [stdout] 33 | std::env::set_var("FORMAT_WITH_ZEROS", "false"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 33 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 34 ~ unsafe { std::env::set_var("FORMAT_WITH_ZEROS", "false") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:35:9 [INFO] [stdout] | [INFO] [stdout] 35 | std::env::remove_var("FORMAT_WITH_ZEROS"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 35 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 36 ~ unsafe { std::env::remove_var("FORMAT_WITH_ZEROS") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:40:9 [INFO] [stdout] | [INFO] [stdout] 40 | std::env::remove_var("DO_CLEANUP"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 40 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 41 ~ unsafe { std::env::remove_var("DO_CLEANUP") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | std::env::set_var("DO_CLEANUP", "false"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 42 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 43 ~ unsafe { std::env::set_var("DO_CLEANUP", "false") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:44:9 [INFO] [stdout] | [INFO] [stdout] 44 | std::env::remove_var("DO_CLEANUP"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 44 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 45 ~ unsafe { std::env::remove_var("DO_CLEANUP") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 46 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating examples/add-key-to-persistent-keyring.rs from 2021 edition to 2024 [INFO] [stderr] Migrating examples/cryptsetup-luks2.rs from 2021 edition to 2024 [INFO] [stderr] Migrating examples/format-luks2-with-token.rs from 2021 edition to 2024 [INFO] [stderr] Migrating examples/label_and_uuid.rs from 2021 edition to 2024 [INFO] [stderr] Migrating examples/callback_macro.rs from 2021 edition to 2024 [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 11.64s [INFO] [stderr] Running `cargo check` to verify 2024 [INFO] [stderr] Compiling libcryptsetup-rs v0.10.0 (/tmp/fixit) [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/lib.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/consts/flags.rs:31:15 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:33:15 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:35:15 [INFO] [stdout] | [INFO] [stdout] 35 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:37:15 [INFO] [stdout] | [INFO] [stdout] 37 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:39:15 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/luks2/reencrypt.rs:193:11 [INFO] [stdout] | [INFO] [stdout] 193 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:9:7 [INFO] [stdout] | [INFO] [stdout] 9 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:68:7 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:102:7 [INFO] [stdout] | [INFO] [stdout] 102 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:121:7 [INFO] [stdout] | [INFO] [stdout] 121 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 101 | memzero!(SafeOwnedMemZero); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 150 | memzero!(SafeMemHandle); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:134:11 [INFO] [stdout] | [INFO] [stdout] 134 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/lib.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/consts/flags.rs:31:15 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:33:15 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:35:15 [INFO] [stdout] | [INFO] [stdout] 35 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:37:15 [INFO] [stdout] | [INFO] [stdout] 37 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:39:15 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/consts/flags.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup24supported` [INFO] [stdout] --> src/luks2/reencrypt.rs:193:11 [INFO] [stdout] | [INFO] [stdout] 193 | #[cfg(cryptsetup24supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup24supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup24supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:9:7 [INFO] [stdout] | [INFO] [stdout] 9 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:68:7 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:102:7 [INFO] [stdout] | [INFO] [stdout] 102 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:121:7 [INFO] [stdout] | [INFO] [stdout] 121 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | #[cfg(all(test, cryptsetup23supported, feature = "mutex"))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 75 | / define_handle! { [INFO] [stdout] 76 | | /// Handle for zeroing owned memory. "Owned" in this context refers to memory [INFO] [stdout] 77 | | /// that has been allocated and stored in some kind of `char **` argument [INFO] [stdout] 78 | | /// in the context of C FFI. This means that the memory has been allocated [INFO] [stdout] ... | [INFO] [stdout] 99 | | } [INFO] [stdout] 100 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 101 | memzero!(SafeOwnedMemZero); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:15:15 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:18:15 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:26:15 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 105 | / define_handle! { [INFO] [stdout] 106 | | /// Handle for zeroing borrowed memory. "Borrowed" in this context refers to memory [INFO] [stdout] 107 | | /// that will be cleaned up by some other scope and is not required to be freed [INFO] [stdout] 108 | | /// by the caller. An example of this would be a `char *` pointer to kernel memory [INFO] [stdout] ... | [INFO] [stdout] 118 | | from_ptr [INFO] [stdout] 119 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `define_handle` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 120 | memzero!(SafeBorrowedMemZero); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:41:15 [INFO] [stdout] | [INFO] [stdout] 41 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 150 | memzero!(SafeMemHandle); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `memzero` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `cryptsetup23supported` [INFO] [stdout] --> src/mem.rs:134:11 [INFO] [stdout] | [INFO] [stdout] 134 | #[cfg(cryptsetup23supported)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(cryptsetup23supported)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(cryptsetup23supported)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:31:9 [INFO] [stdout] | [INFO] [stdout] 31 | std::env::remove_var("FORMAT_WITH_ZEROS"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:33:9 [INFO] [stdout] | [INFO] [stdout] 33 | std::env::set_var("FORMAT_WITH_ZEROS", "false"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:35:9 [INFO] [stdout] | [INFO] [stdout] 35 | std::env::remove_var("FORMAT_WITH_ZEROS"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 23 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:40:9 [INFO] [stdout] | [INFO] [stdout] 40 | std::env::remove_var("DO_CLEANUP"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | std::env::set_var("DO_CLEANUP", "false"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0133]: call to unsafe function `remove_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/tests/mod.rs:44:9 [INFO] [stdout] | [INFO] [stdout] 44 | std::env::remove_var("DO_CLEANUP"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 6 previous errors; 23 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0133`. [INFO] [stdout] [INFO] [stderr] error: could not compile `libcryptsetup-rs` (lib test) due to 7 previous errors; 23 warnings emitted [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error: failed to check after updating to 2024 [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `cargo check --frozen --all --all-targets --message-format=json` (exit status: 101) [INFO] running `Command { std: "docker" "inspect" "a13a57950d206fd14a4d74461537afed61c7ccfebbfbf2c01efcf6a59163b137", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a13a57950d206fd14a4d74461537afed61c7ccfebbfbf2c01efcf6a59163b137", kill_on_drop: false }` [INFO] [stdout] a13a57950d206fd14a4d74461537afed61c7ccfebbfbf2c01efcf6a59163b137