| commit | f5cbdbc2b945dbb7702d2dfbee62e4b70559fd99 | [log] [tgz] |
|---|---|---|
| author | gnzlbg <gonzalobg88@gmail.com> | Fri Feb 22 14:10:52 2019 +0100 |
| committer | gnzlbg <gonzalobg88@gmail.com> | Fri Feb 22 19:18:02 2019 +0100 |
| tree | 4950ebf05330f0f405898a080a2fd585e5c6e2bd | |
| parent | 8c571e0ce930d726322a0b02e69f5dc0b8b9ca74 [diff] |
Clean libc-test for apple targets This cleans up the build.rs of `libc-test` for apple targets. I wanted to update the docker containers of some targets so that we can start testing newer currently-skipped APIs properly, but it is impossible to figure out which headers and APIs are skipped for each target. This PR separates the testing of apple targets into its own self-contained function. This allows seeing exactly which headers are included, and which items are skipped. A lot of work will be required to separate the testing of all major platforms and make the script reasonable. During the clean up, I discovered that, at least for apple targets, deprecated but not removed APIs are not tested. I re-enabled testing for those, and fixed `daemon`, which was not properly linking its symbol. I also added the `#[deprecated]` attribute to the `#[deprecated]` APIs of the apple targets. The attribute is available since Rust 1.9.0 and the min. Rust version we support is Rust 1.13.0. Many other APIs are also currently not tested "because they are weird" which I interpret as "the test failed for an unknown reason", as a consequence: * the signatures of execv, execve, and execvp are incorrect (see https://github.com/rust-lang/libc/issues/1272) * the `sig_t` type is called `sighandler_t` in libc for some reason: https://github.com/rust-lang/libc/issues/1273 This probably explains why some other things, like the `sa_handler`/`sa_sigaction` fields of `sigaction` were skipped. The field is actually a union, which can be either a `sig_t` for the `sa_handler` field, or some other type for the `sa_sigaction` field, but because the distinction was not made, the field was not checked. The latest ctest version can check volatile pointers, so a couple of skipped tests are now tested using this feature.
- libc-test/build.rs[diff]
- libc-test/test/linux_fcntl.rs[diff]
- libc-test/test/main.rs[diff]
- src/unix/bsd/apple/mod.rs[diff]
- src/unix/bsd/freebsdlike/mod.rs[diff]
- src/unix/bsd/mod.rs[diff]
- src/unix/bsd/netbsdlike/mod.rs[diff]
- src/unix/haiku/mod.rs[diff]
- src/unix/hermit/mod.rs[diff]
- src/unix/mod.rs[diff]
- src/unix/newlib/mod.rs[diff]
- src/unix/notbsd/mod.rs[diff]
- src/unix/solarish/mod.rs[diff]
- src/unix/uclibc/mod.rs[diff]
- ci/
- libc-test/
- src/
- .cirrus.yml
- .gitignore
- .travis.yml
- appveyor.yml
- build.rs
- Cargo.toml
- CONTRIBUTING.md
- LICENSE-APACHE
- LICENSE-MIT
- README.md
- rustfmt.toml
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 defaultlibclinks to the standard library. Disable this feature remove this dependency and be able to uselibcin#![no_std]crates.extra_traits: allstructs implemented inlibcareCopyandClone. This feature derivesDebug,Eq,Hash, andPartialEq.
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.