OpenE2K/libc-rs
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2,897 Commits 2 Branches 0 Tags 10 MiB
Rust 98%
Shell 1%
Dockerfile 0.7%
CSS 0.3%
759c837611
Go to file
gnzlbg 759c837611 [breaking change] incorrect API of gettimeofday 
The second argument of `gettimeofday` was a `*mut c_void` on all targets,
but that type is incorrect in the following targets, where it should be
a `*mut timezone` instead:

On these other targets it appears that the signature of gettimeofday was incorrect (it takes a time-zone pointer instead of a void pointer):

linux+gnu: http://man7.org/linux/man-pages/man2/gettimeofday.2.html
freebsd: https://www.freebsd.org/cgi/man.cgi?query=gettimeofday&apropos=0&sektion=2&manpath=FreeBSD+11.2-stable&arch=default&format=html
openbsd: https://man.openbsd.org/gettimeofday.2
android: https://github.com/ricardoquesada/android-ndk/blob/master/usr/include/sys/time.h
dragonfly: https://www.dragonflybsd.org/cgi/web-man?command=gettimeofday&section=2

This commit corrects the type on these targets, which is a breaking change. Due
to how this API is commonly used (e.g. passing `ptr::null_mut` to the second
argument), breakage should be minimal. Users wanting to support both versions
can just write `ptr as *mut _` instead.

Closes #1338.
2019-05-22 10:39:06 +02:00
.github Avoid the template showing up in the issues 2019-04-07 14:26:03 +02:00
ci Auto merge of #1335 - leo60228:patch-1, r=gnzlbg 2019-05-16 11:19:32 +00:00
libc-test [breaking change] incorrect API of gettimeofday 2019-05-22 10:39:06 +02:00
src [breaking change] incorrect API of gettimeofday 2019-05-22 10:39:06 +02:00
.cirrus.yml
.gitignore
.travis.yml Auto merge of #1335 - leo60228:patch-1, r=gnzlbg 2019-05-16 11:19:32 +00:00
appveyor.yml Cleanup Windows libc-test build.rs 2019-02-24 13:11:14 +01:00
build.rs Fix build on all platforms 2019-02-07 13:44:32 +01:00
Cargo.toml Bump version to 0.2.55 2019-05-16 06:53:06 -06:00
CONTRIBUTING.md Generate a proper landing page for the master docs 2019-02-13 14:48:50 +01:00
LICENSE-APACHE
LICENSE-MIT
README.md Fix broken links in README 2019-02-21 10:18:06 +01:00
rustfmt.toml Check style using rustfmt and reformat 2019-02-07 11:13:38 +01:00

README.md

Travis-CI Status Appveyor Status Cirrus-CI Status Latest Version Documentation License

libc - Raw FFI bindings to platforms' system libraries

libc provides all of the definitions necessary to easily interoperate with C code (or "C-like" code) on each of the platforms that Rust supports. This includes type definitions (e.g. c_int), constants (e.g. EINVAL) as well as function headers (e.g. malloc).

This crate exports all underlying platform types, functions, and constants under the crate root, so all items are accessible as libc::foo. The types and values of all the exported APIs match the platform that libc is compiled for.

More detailed information about the design of this library can be found in its associated RFC.

Usage

Add the following to your Cargo.toml:

[dependencies]
libc = "0.2"

Features

  • use_std: by default libc links to the standard library. Disable this feature remove this dependency and be able to use libc in #![no_std] crates.

  • extra_traits: all structs implemented in libc are Copy and Clone. This feature derives Debug, Eq, Hash, and PartialEq.

Rust version support

The minimum supported Rust toolchain version is Rust 1.13.0 . APIs requiring newer Rust features are only available on newer Rust toolchains:

Feature Version
union 1.19.0
const mem::size_of 1.24.0
repr(align) 1.25.0
extra_traits 1.25.0
core::ffi::c_void 1.30.0
repr(packed(N)) 1.33.0

Platform support

Platform-specific documentation (master branch).

See ci/build.sh for the platforms on which libc is guaranteed to build for each Rust toolchain. The test-matrix at Travis-CI, Appveyor, and Cirrus-CI show the platforms in which libc tests are run.

License

This project is licensed under either of

at your option.

Contributing

We welcome all people who want to contribute. Please see the contributing instructions for more information.

Contributions in any form (issues, pull requests, etc.) to this project must adhere to Rust's Code of Conduct.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in libc by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.