i686-linux-android libc and libstd disagree on c_char #561
Comments
|
This was fixed when rust libc was update to 0.2.21. See rust-lang/rust#40903. Using rustc nightly (2017-03-29) should make your code compile. |
|
Such timing! I'll give it a try |
|
it works 👍 |
danielverkamp
pushed a commit
to danielverkamp/libc
that referenced
this issue
Apr 28, 2020
Currently these are gated by the `atomics` feature unconditionally, but that may be tweaked in the future! Otherwise this should enable building out some primitives in the standard library using these intrinsics.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So std lib seems to be wrong about this. but what to do? a lot of things just don't compile (looking at openssl) because of CString and CStr
libstd says that
c_charisu8https://github.com/rust-lang/rust/blob/b1363a73ede57ae595f3a1be2bb75d308ba4f7f6/src/libstd/os/raw.rs#L15
libc says that
c_charisi8https://github.com/rust-lang/libc/blob/master/src/unix/notbsd/android/b32/x86.rs#L1
The text was updated successfully, but these errors were encountered: