You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a new project where junction is the only dependency, I get the following build failures on Windows 11 with Rust 1.67.0 (fc594f156 2023-01-24). I do not see these errors when running cargo build in the library directory; it's entirely possible I'm doing something wrong.
Similar failures seem to have happened in wezterm and tokio.
cargo build --target x86_64-pc-windows-msvc
Compiling junction v0.2.0error[E0308]: mismatched types
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals.rs:78:32
|
78 | helpers::set_reparse_point(file.as_raw_handle(), rdb, u32::from(in_buffer_size))
| -------------------------- ^^^^^^^^^^^^^^^^^^^^ expected enum `winapi::ctypes::c_void`, found enum `std::ffi::c_void`
| |
| arguments to this function are incorrect
|
= note:enum `std::ffi::c_void` and enum `winapi::ctypes::c_void` have similar names, but are actually distinct types
note:enum `std::ffi::c_void` is defined in crate `core`
--> C:\Users\james\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\ffi\mod.rs:203:1
|
203 | pub enum c_void {
| ^^^^^^^^^^^^^^^
note:enum `winapi::ctypes::c_void` is defined in crate `winapi`
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\winapi-0.3.9\src\lib.rs:38:5
|
38 | pub enum c_void{}
| ^^^^^^^^^^^^^^^
note: function defined here
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals\helpers.rs:121:8
|
121 | pub fn set_reparse_point(handle:HANDLE, rdb:*mut ReparseDataBuffer, len: u32) -> io::Result<()> {
| ^^^^^^^^^^^^^^^^^ --------------
error[E0308]:mismatched types
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals.rs:83:35
|
83 | helpers::delete_reparse_point(file.as_raw_handle())
| ----------------------------- ^^^^^^^^^^^^^^^^^^^^ expected enum `winapi::ctypes::c_void`, found enum `std::ffi::c_void`
| |
| ^^^^^^^^^^^^^^^
note:enum `winapi::ctypes::c_void` is defined in crate `winapi`
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\winapi-0.3.9\src\lib.rs:38:5
|
38 | pub enum c_void{}
| ^^^^^^^^^^^^^^^
note: function defined here
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals\helpers.rs:142:8
|
142 | pub fn delete_reparse_point(handle:HANDLE) -> io::Result<()> {
| ^^^^^^^^^^^^^^^^^^^^ --------------
error[E0308]:mismatched types
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals.rs:93:47
|
93 | let rdb = helpers::get_reparse_data_point(file.as_raw_handle(),&mut data)?;
| ------------------------------- ^^^^^^^^^^^^^^^^^^^^ expected enum `winapi::ctypes::c_void`, found enum `std::ffi::c_void`
| |
| arguments to this function are incorrect
| = note:enum `std::ffi::c_void` and enum `winapi::ctypes::c_void` have similar names, but are actually distinct typesnote:enum `std::ffi::c_void` is defined in crate `core`
--> C:\Users\james\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\ffi\mod.rs:203:1
|
203 | pub enum c_void {
| ^^^^^^^^^^^^^^^
note:enum `winapi::ctypes::c_void` is defined in crate `winapi`
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\winapi-0.3.9\src\lib.rs:38:5
|
38 | pub enum c_void{}
| ^^^^^^^^^^^^^^^
note: function defined here
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals\helpers.rs:97:8
|
97 | pub fn get_reparse_data_point<'a>(handle:HANDLE, data:&'a mut [u8]) -> io::Result<&'a ReparseDataBuffer> {
| ^^^^^^^^^^^^^^^^^^^^^^ --------------
error[E0308]: mismatched types
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals.rs:104:47
|
104 | let rdb = helpers::get_reparse_data_point(file.as_raw_handle(),&mut data)?;
| ------------------------------- ^^^^^^^^^^^^^^^^^^^^ expected enum `winapi::ctypes::c_void`, found enum `std::ffi::c_void`
| |
| arguments to this function are incorrect
|
= note:enum `std::ffi::c_void` and enum `winapi::ctypes::c_void` have similar names, but are actually distinct typesnote:enum `std::ffi::c_void` is defined in crate `core` --> C:\Users\james\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\ffi\mod.rs:203:1
|
203 | pub enum c_void {
| ^^^^^^^^^^^^^^^
note:enum `winapi::ctypes::c_void` is defined in crate `winapi`
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\winapi-0.3.9\src\lib.rs:38:5
|
38 | pub enum c_void{}
| ^^^^^^^^^^^^^^^
note: function defined here
--> C:\Users\james\.cargo\registry\src\github.com-1ecc6299db9ec823\junction-0.2.0\src\internals\helpers.rs:97:8
|
97 | pub fn get_reparse_data_point<'a>(handle:HANDLE, data:&'a mut [u8]) -> io::Result<&'a ReparseDataBuffer> {
| ^^^^^^^^^^^^^^^^^^^^^^ --------------
The text was updated successfully, but these errors were encountered:
In a new project where
junction
is the only dependency, I get the following build failures on Windows 11 with Rust 1.67.0 (fc594f156 2023-01-24). I do not see these errors when runningcargo build
in the library directory; it's entirely possible I'm doing something wrong.Similar failures seem to have happened in wezterm and tokio.
The text was updated successfully, but these errors were encountered: