-
Notifications
You must be signed in to change notification settings - Fork 140
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
Makedev was unmarked as unsafe in libc 0.2.133 (latest) #402
Comments
#403 is now merged, and the fix is included in the 0.35.10 release. |
sunfishcode
added a commit
to sunfishcode/wasmtime
that referenced
this issue
Sep 21, 2022
This is primarily to pull in bytecodealliance/cap-std#271, the fix for bytecodealliance#4936, compilation on Rust nightly on Windows. It also updates to rustix 0.35.10, to pull in bytecodealliance/rustix#403, the fix for bytecodealliance/rustix#402, compilation on newer versions of the libc crate, which changed a public function from `unsafe` to safe. Fixes bytecodealliance#4936.
alexcrichton
pushed a commit
to bytecodealliance/wasmtime
that referenced
this issue
Sep 21, 2022
* Update to cap-std 0.26. This is primarily to pull in bytecodealliance/cap-std#271, the fix for #4936, compilation on Rust nightly on Windows. It also updates to rustix 0.35.10, to pull in bytecodealliance/rustix#403, the fix for bytecodealliance/rustix#402, compilation on newer versions of the libc crate, which changed a public function from `unsafe` to safe. Fixes #4936. * Update the system-interface audit for 0.23. * Update the libc supply-chain config version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the current checks are failing because https://docs.rs/libc/0.2.133/libc/fn.makedev.html removed the unsafe (see https://docs.rs/libc/0.2.132/libc/fn.makedev.html )
The text was updated successfully, but these errors were encountered: