-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable "std" feature on linux-raw-sys when "std" feature is enabled #945
Comments
This currently means that
|
Keep dash-mpd at 0.14.5 and xattr at 1.0.1 because otherwise compilation fails, see: - Stebalien/xattr#44 - bytecodealliance/rustix#945 Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/1404>
This reverts rustix support until enabling the "std" feature no longer causes downstream breakage. See: - bytecodealliance/rustix#945 - #44
I'm having this same issue. Our build suddently is broken: error[E0308]: mismatched types
--> /home/vscode/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustix-0.38.27/src/backend/linux_raw/net/addr.rs:39:32
|
39 | unix.sun_path[i] = *b;
| ---------------- ^^ expected `i8`, found `u8`
| |
| expected due to the type of this binding
error[E0308]: mismatched types
--> /home/vscode/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustix-0.38.27/src/backend/linux_raw/net/addr.rs:52:32
|
52 | id.copy_from_slice(name);
| --------------- ^^^^ expected `&[i8]`, found `&[u8]`
| |
| arguments to this method are incorrect
|
= note: expected reference `&[i8]`
found reference `&[u8]`
note: method defined here
--> /rustc/9d871b0617a4b3d6610b7cee0ab5310dcb542c62/library/core/src/slice/mod.rs:3331:12 |
BTW Possible temporal quick and dirty fix: depend on |
xattr 1.1.1 has been released with a fix (reverts the change). I've yanked 1.1.0 now to prevent his from spreading. |
(unless your issue is unrelated to xattr) |
I've now submitted #971 with a fix for this. |
#971 is now released in rustix 0.38.28. |
As "std" changes API details from
linux-raw-sys
that is exposed in the public API, this would be a breaking change.cc #753
The text was updated successfully, but these errors were encountered: