rust-libc/libc-test
bors 19f3be3638 Auto merge of #578 - cactorium:master, r=alexcrichton
Steps towards support for musl-unknown-linux-uclibc

Hello! I've been working towards resolving https://github.com/rust-lang/libc/issues/361 , this PR compiles successfully with a newish compiler (with some minor fixes in `gcc`, `ctest`), and all the tests pass for `libc-ctest`. Basically most of the undefined functions, constants, and structs were just removed from the ctest, and then any constants that weren't correct were fixed. Would it make more sense to conditionally remove them from libc? I wasn't sure when it was appropriate to skip the test for it instead of removing the function/constants, so I just removed all the tests for now because that was a little easier than hunting them down. I'm also guessing the way some of the constants were conditionally set wasn't the correct style, would you guys have any advice on how to do it more correctly? Lemme know how it looks!
2017-05-08 14:49:12 +00:00
..
generate-files Try to fix powerpc64 and update to crates.io ctest 2016-10-20 17:23:23 -07:00
src Add OpenBSD and FreeBSD CI to Travis 2016-01-18 22:54:28 -08:00
build-generated.rs libc-test: allow deprecated functions 2016-08-09 14:38:11 +08:00
build.rs Auto merge of #578 - cactorium:master, r=alexcrichton 2017-05-08 14:49:12 +00:00
Cargo.toml Try to fix powerpc64 and update to crates.io ctest 2016-10-20 17:23:23 -07:00
run-generated-Cargo.toml Add OpenBSD and FreeBSD CI to Travis 2016-01-18 22:54:28 -08:00