Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
add support for mips-uclibc targets #361
These targets landed in rust-lang/rust#35734 but this crate doesn't properly support them. This
Here are instructions on how to run said test suite:
I've created a docker image (*) with all the stuff needed (e.g. cross toolchain) to run the test
Then, inside docker container run this command:
To cross compile
UPDATE: The image is now up. Disregard the note below.
(*) NOTE: I'm still uploading the image and it may take a while. In the meantime you can build the image
Signal enum This is work in progress. I post this pull request as a request for discussion. I mark the lines I have doubts or ideas about. Ignore the first commit. It is the same as PR rust-lang#361, which I wanted to base this change off.
Steps towards support for musl-unknown-linux-uclibc Hello! I've been working towards resolving #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!
@japaric when I run