[INFO] fetching crate thindx-xinput 0.0.0-2024-02-04... [INFO] testing thindx-xinput-0.0.0-2024-02-04 against master#cdb45c87e2cd43495379f7e867e3cc15dcee9f93 for pr-145838-1 [INFO] extracting crate thindx-xinput 0.0.0-2024-02-04 into /workspace/builds/worker-3-tc1/source [INFO] removed /workspace/builds/worker-3-tc1/source/rust-toolchain.toml [INFO] started tweaking crates.io crate thindx-xinput 0.0.0-2024-02-04 [INFO] finished tweaking crates.io crate thindx-xinput 0.0.0-2024-02-04 [INFO] tweaked toml for crates.io crate thindx-xinput 0.0.0-2024-02-04 written to /workspace/builds/worker-3-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate thindx-xinput 0.0.0-2024-02-04 on toolchain cdb45c87e2cd43495379f7e867e3cc15dcee9f93 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate thindx-xinput 0.0.0-2024-02-04 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" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] a984b110e7205bdf567fbb3682bd99cbd984a36fda8344413e48ac9186d7ef6b [INFO] running `Command { std: "docker" "start" "-a" "a984b110e7205bdf567fbb3682bd99cbd984a36fda8344413e48ac9186d7ef6b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a984b110e7205bdf567fbb3682bd99cbd984a36fda8344413e48ac9186d7ef6b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a984b110e7205bdf567fbb3682bd99cbd984a36fda8344413e48ac9186d7ef6b", kill_on_drop: false }` [INFO] [stdout] a984b110e7205bdf567fbb3682bd99cbd984a36fda8344413e48ac9186d7ef6b [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 618c2f2094f3ed9ea88bb2a058c143f6b5f6ec40d7e8c205bc3e0e0885d19d30 [INFO] running `Command { std: "docker" "start" "-a" "618c2f2094f3ed9ea88bb2a058c143f6b5f6ec40d7e8c205bc3e0e0885d19d30", kill_on_drop: false }` [INFO] [stderr] Compiling thindx-xinput v0.0.0-2024-02-04 (/opt/rustwide/workdir) [INFO] [stdout] error[E0433]: failed to resolve: could not find `windows` in `os` [INFO] [stdout] --> src/dll/imports.rs:11:14 [INFO] [stdout] | [INFO] [stdout] 11 | use std::os::windows::ffi::OsStrExt; [INFO] [stdout] | ^^^^^^^ could not find `windows` in `os` [INFO] [stdout] | [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> /rustc/cdb45c87e2cd43495379f7e867e3cc15dcee9f93/library/std/src/os/mod.rs:56:5 [INFO] [stdout] | [INFO] [stdout] = note: the item is gated here [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> /rustc/cdb45c87e2cd43495379f7e867e3cc15dcee9f93/library/std/src/os/mod.rs:120:10 [INFO] [stdout] | [INFO] [stdout] = note: the item is gated here [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `windows` in `os` [INFO] [stdout] --> src/functions/get_audio_device_ids_.rs:4:14 [INFO] [stdout] | [INFO] [stdout] 4 | use std::os::windows::ffi::*; [INFO] [stdout] | ^^^^^^^ could not find `windows` in `os` [INFO] [stdout] | [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> /rustc/cdb45c87e2cd43495379f7e867e3cc15dcee9f93/library/std/src/os/mod.rs:56:5 [INFO] [stdout] | [INFO] [stdout] = note: the item is gated here [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> /rustc/cdb45c87e2cd43495379f7e867e3cc15dcee9f93/library/std/src/os/mod.rs:120:10 [INFO] [stdout] | [INFO] [stdout] = note: the item is gated here [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/battery_devtype.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/battery_level.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/battery_type.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/devsubtype.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/devtype.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/enumerations/vk.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/flags/buttons.rs:5:5 [INFO] [stdout] | [INFO] [stdout] 5 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/flags/caps.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/flags/flag.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/flags/keystroke.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `winresult` [INFO] [stdout] --> src/error.rs:7:5 [INFO] [stdout] | [INFO] [stdout] 7 | use winresult::{*, ErrorCode}; [INFO] [stdout] | ^^^^^^^^^ use of unresolved module or unlinked crate `winresult` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winresult`, use `cargo add winresult` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/functions/get_battery_information_.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::Zeroable; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/functions/get_capabilities_.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::Zeroable; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/functions/get_dsound_audio_device_guids_.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::Zeroable; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/functions/get_keystroke_.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::Zeroable; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/functions/get_state_.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::Zeroable; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/battery_information.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/capabilities.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/structures/gamepad.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::um::xinput::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/dsound_audio_device_guids.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::*; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/keystroke.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/state.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/vibration.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/dll/imports.rs:7:5 [INFO] [stdout] | [INFO] [stdout] 7 | use winapi::shared::minwindef::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/dll/imports.rs:8:5 [INFO] [stdout] | [INFO] [stdout] 8 | use winapi::um::libloaderapi::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/dll/imports.rs:9:5 [INFO] [stdout] | [INFO] [stdout] 9 | use winapi::um::winnt::*; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `minidl` [INFO] [stdout] --> src/dll/imports.rs:5:5 [INFO] [stdout] | [INFO] [stdout] 5 | use minidl::Library; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `minidl` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `minidl`, use `cargo add minidl` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/battery_devtype.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/battery_level.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/battery_type.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/devsubtype.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/devtype.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/enumerations/vk.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/flags/buttons.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/flags/caps.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/flags/flag.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `winapi` [INFO] [stdout] --> src/structures/dsound_audio_device_guids.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use winapi::shared::guiddef::GUID; [INFO] [stdout] | ^^^^^^ use of unresolved module or unlinked crate `winapi` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `winapi`, use `cargo add winapi` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/flags/keystroke.rs:1:5 [INFO] [stdout] | [INFO] [stdout] 1 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `bytemuck` [INFO] [stdout] --> src/structures/gamepad.rs:3:5 [INFO] [stdout] | [INFO] [stdout] 3 | use bytemuck::{Pod, Zeroable}; [INFO] [stdout] | ^^^^^^^^ use of unresolved module or unlinked crate `bytemuck` [INFO] [stdout] | [INFO] [stdout] = help: if you wanted to use a crate named `bytemuck`, use `cargo add bytemuck` to add it to your `Cargo.toml` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: cannot find derive macro `Pod` in this scope [INFO] [stdout] --> src/structures/dsound_audio_device_guids.rs:51:19 [INFO] [stdout] | [INFO] [stdout] 51 | #[derive(Default, Pod, Zeroable)] [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: cannot find derive macro `Zeroable` in this scope [INFO] [stdout] --> src/structures/dsound_audio_device_guids.rs:51:24 [INFO] [stdout] | [INFO] [stdout] 51 | #[derive(Default, Pod, Zeroable)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg` [INFO] [stdout] --> src/_lib.rs:4:13 [INFO] [stdout] | [INFO] [stdout] 4 | #![cfg_attr(doc_cfg, feature(doc_cfg))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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(doc_cfg)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` 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 value: `winapi-0-1` [INFO] [stdout] --> src/interop/_interop.rs:5:7 [INFO] [stdout] | [INFO] [stdout] 5 | #[cfg(feature = "winapi-0-1")] #[path = "winapi-0.1.rs"] mod winapi_0_1; [INFO] [stdout] | ^^^^^^^^^^------------ [INFO] [stdout] | | [INFO] [stdout] | help: there is a expected value with a similar name: `"winapi-0-3"` [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `winapi-0-1` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/battery_devtype.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | enumish! { BatteryDevType => u8; default: Gamepad == 0; Gamepad, Headset } [INFO] [stdout] | -------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/battery_level.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | enumish! { BatteryLevel => u8; default: Empty == 0; Empty, Low, Medium, Full } [INFO] [stdout] | ------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/battery_type.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | enumish! { BatteryType => u8; default: Disconnected == 0; Disconnected, Wired, Alkaline, NiMH, Unknown } [INFO] [stdout] | -------------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/devsubtype.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | enumish! { DevSubType => u8; Unknown, Gamepad, Wheel, ArcadeStick, FlightStick, DancePad, Guitar, GuitarAlternate, DrumKit, GuitarBass, ArcadePad } [INFO] [stdout] | --------------------------------------------------------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/devtype.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | enumish! { DevType => u8; Gamepad } [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:211:15 [INFO] [stdout] | [INFO] [stdout] 211 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/enumerations/vk.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / enumish! { [INFO] [stdout] 13 | | VK => u16; [INFO] [stdout] 14 | | None, PadA, PadB, PadX, PadY, PadRShoulder, PadLShoulder, PadRTrigger, PadLTrigger, [INFO] [stdout] 15 | | PadDPadUp, PadDPadDown, PadDPadLeft, PadDPadRight, PadStart, PadBack, PadLThumbPress, PadRThumbPress, [INFO] [stdout] 16 | | PadLThumbUp, PadLThumbDown, PadLThumbRight, PadLThumbLeft, PadLThumbUpLeft, PadLThumbUpRight, PadLThumbDownRight, PadLThumbDownLeft, [INFO] [stdout] 17 | | PadRThumbUp, PadRThumbDown, PadRThumbRight, PadRThumbLeft, PadRThumbUpLeft, PadRThumbUpRight, PadRThumbDownRight, PadRThumbDownLeft, [INFO] [stdout] 18 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `enumish` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:277:15 [INFO] [stdout] | [INFO] [stdout] 277 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/flags/buttons.rs:20:1 [INFO] [stdout] | [INFO] [stdout] 20 | flags! { Buttons => u16; None, DPadUp, DPadDown, DPadLeft, DPadRight, Start, Guide, Back, LeftThumb, RightThumb, LeftShoulder, RightShoulder, A, B, X, Y } [INFO] [stdout] | ---------------------------------------------------------------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `flags` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:277:15 [INFO] [stdout] | [INFO] [stdout] 277 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/flags/caps.rs:17:1 [INFO] [stdout] | [INFO] [stdout] 17 | flags! { Caps => u16; None, VoiceSupported, FfbSupported, Wireless, PmdSupported, NoNavigation } [INFO] [stdout] | ------------------------------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `flags` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:277:15 [INFO] [stdout] | [INFO] [stdout] 277 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/flags/flag.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | flags! { Flag => u32; None, Gamepad } [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `flags` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `impl-from-unchecked` [INFO] [stdout] --> src/macros.rs:277:15 [INFO] [stdout] | [INFO] [stdout] 277 | #[cfg(feature = "impl-from-unchecked")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/flags/keystroke.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | flags! { Keystroke => u16; None, KeyDown, KeyUp, Repeat } [INFO] [stdout] | --------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `undocumented`, `winapi-0-2`, `winapi-0-3`, `windows-0-22`, `windows-0-23`, `windows-0-24`, `windows-0-25`, `windows-0-26`, `windows-0-27`, `windows-0-28`, `windows-0-29`, `windows-0-30`, `windows-0-32`, `windows-0-33`, `windows-0-34`, `windows-0-35`, `windows-0-36`, `windows-0-37`, `windows-0-38`, `windows-0-39`, `windows-0-40`, `windows-0-41`, `windows-0-42`, `windows-0-43`, `windows-0-44`, `windows-0-46`, `windows-0-48`, `windows-0-51`, `windows-0-52`, `windows-sys-0-27`, `windows-sys-0-28`, `windows-sys-0-29`, `windows-sys-0-30`, `windows-sys-0-32`, and `windows-sys-0-33` and 8 more [INFO] [stdout] = help: consider adding `impl-from-unchecked` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `flags` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0433. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `thindx-xinput` (lib) due to 43 previous errors; 12 warnings emitted [INFO] running `Command { std: "docker" "inspect" "618c2f2094f3ed9ea88bb2a058c143f6b5f6ec40d7e8c205bc3e0e0885d19d30", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "618c2f2094f3ed9ea88bb2a058c143f6b5f6ec40d7e8c205bc3e0e0885d19d30", kill_on_drop: false }` [INFO] [stdout] 618c2f2094f3ed9ea88bb2a058c143f6b5f6ec40d7e8c205bc3e0e0885d19d30