For unknown reasons, the Rust libc bindings disagree between signed and
unsigned char among different cpu architectures.
E.g. 32- and 64-bit ARM translate char to u8, while amd64 uses i8.
By using the c_char type provided by the libc bindings, this issue can
be avoided in a cpu and os independent way.
For unknown reasons, the Rust libc bindings disagree between signed and unsigned char among different cpu architectures. E.g. 32- and 64-bit ARM translate char to u8, while amd64 uses i8.
By using the c_char type provided by the libc bindings, this issue can be avoided in a cpu and os independent way.
Fixes #13
Signed-off-by: Josua Mayer josua@solid-run.com