summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Auto merge of #1309 - alexcrichton:bump, r=gnzlbg0.2.51bors2019-03-281-1/+1
|\ | | | | | | | | | | Bump to 0.2.51 Pulls in the new wasi target support!
| * Bump to 0.2.51Alex Crichton2019-03-281-1/+1
| |
* | Auto merge of #1308 - tormol:master, r=gnzlbgbors2019-03-283-1/+3
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | Add mq_getfd_np() on FreeBSD and fix mqd_t on DragonFlyBSD [`mq_getfd_np()` was added in FreeBSD 11](https://svnweb.freebsd.org/base/stable/11/include/mqueue.h?revision=306905&view=markup). I'm already using it in my [posixmq crate](https://github.com/tormol/posixmq) for mio/kqueue integration, and I've tested it both in virtualbox and on Cirrus-CI. [`mqd_t` in an `int` on DragonFlyBSD](https://github.com/DragonFlyBSD/DragonFlyBSD/blob/e7ab884bd49753f8884eb597d10d6569a08fa0df/sys/sys/types.h#L139) even though it's a pointer on FreeBSD, because [DragonflyBSD's implementation is based on NetBSD](https://github.com/DragonFlyBSD/DragonFlyBSD/commit/f2df0f7ca6de3f944dcbfb9923750d7c88984535). The definitions for `mq_attr` are already separate and correct. Does fixing this count as a breaking change? I think the current definition will work in most cases, because IIRC the calling convention means that `mqd_t` is always passed via registers, the upper 32 bits might just contain garbage. I've *not* tested this change on DragonFlyBSD. I want to add mq symbols for solarish, but is the CDDL license compatible with Apache-2.0 and MIT?
| * Correct mqd_t on DragonFlyBSDTorbjørn Birch Moltu2019-03-273-1/+2
| |
| * Add mq_getfd_np() for FreeBSDTorbjørn Birch Moltu2019-03-271-0/+1
| |
* | Auto merge of #1307 - alexcrichton:wasi-pr, r=gnzlbgbors2019-03-286-5/+938
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add intial support for wasm32-unknown-wasi This target is [being proposed][LINK] int he rust-lang/rust repository and this is intended to get coupled with that proposal. The definitions here all match the upstream reference-sysroot definitions and the functions all match the reference sysroot as well. The linkage here is described more in detail on the Rust PR itself, but in general it's similar to musl. Automatic verification has been implemented in the same manner as other targets, and it's been used locally to develop this PR and catch errors in the bindings already written (also to help match the evolving sysroot of wasi). The verification isn't hooked up to CI yet though because there is no wasi target distributed via rustup just yet, but once that's done I'll file a follow-up PR to execute verification on CI. [LINK]: https://github.com/rust-lang/rust/pull/59464
| * Touch up style of wasi.rsAlex Crichton2019-03-272-144/+147
| |
| * Address some PR feedbackAlex Crichton2019-03-274-96/+95
| |
| * Add intiial support for wasm32-unknown-wasiAlex Crichton2019-03-275-5/+936
|/ | | | | | | | | | | | | | | | | | This target is [being proposed][LINK] int he rust-lang/rust repository and this is intended to get coupled with that proposal. The definitions here all match the upstream reference-sysroot definitions and the functions all match the reference sysroot as well. The linkage here is described more in detail on the Rust PR itself, but in general it's similar to musl. Automatic verification has been implemented in the same manner as other targets, and it's been used locally to develop this PR and catch errors in the bindings already written (also to help match the evolving sysroot of wasi). The verification isn't hooked up to CI yet though because there is no wasi target distributed via rustup just yet, but once that's done I'll file a follow-up PR to execute verification on CI. [LINK]:
* Auto merge of #1306 - gnzlbg:fix_asmjs, r=gnzlbgbors2019-03-264-72/+119
|\ | | | | | | | | | | Don't fix asmjs and wasm32 build jobs This doesn't fix the jobs, but at least now libc-test reports no errors, even though they still fail to link.
| * Fix buildgnzlbg2019-03-262-14/+14
| |
| * Move inotify to the linux and android sub-modulesgnzlbg2019-03-263-44/+84
| |
| * Move IPV6_FLOW... constants to the linux and android sub-modulesgnzlbg2019-03-253-6/+10
| |
| * Move inotify_event to the linux and android sub-modulesgnzlbg2019-03-254-22/+25
|/
* Auto merge of #1301 - dingelish:master, r=gnzlbgbors2019-03-111-1/+1
|\ | | | | | | | | | | | | | | Add essential target_vendor check for sgx As discussed in issue [57231](https://github.com/rust-lang/rust/issues/57231), the current `sgx` branch only works for Fortanix's sgx platform. So the `target_vendor` should be checked here. Signed-off-by: Yu Ding <dingelish@gmail.com>
| * Add essential target_vendor check for sgxYu Ding2019-03-081-1/+1
|/ | | | Signed-off-by: Yu Ding <dingelish@gmail.com>
* Auto merge of #1299 - leo60228:master, r=gnzlbg0.2.50bors2019-03-051-1/+1
|\ | | | | | | | | | | Bump to 0.2.50 I'm using libnx-rs too, and it'd be nice to have #1278 in a release.
| * Bump libc versionleo602282019-03-041-1/+1
|/
* Auto merge of #1297 - mati865:docker-images-working, r=gnzlbgbors2019-03-0310-11/+11
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upgrade bunch of EOL docker images to Ubuntu 18.04 When upgrading other Dockerfiles (not modified in this PR) they fail with different errors: https://travis-ci.com/mati865/libc/jobs/181623075 https://travis-ci.com/mati865/libc/jobs/181623059 https://travis-ci.com/mati865/libc/jobs/181623067 I think it's because of these 2 commits in glibc: https://sourceware.org/git/?p=glibc.git;a=commit;h=b05cb613e7ae507680c8d914b3e788eea782c0d6 https://sourceware.org/git/?p=glibc.git;a=commit;h=2dba5ce7b8115d6a2789bf279892263621088e74 I have no idea how to fix them so leaving it for somebody who knows what to do.
| * Bump NFT_*_MAXNAMELEN to 256 for PPCMateusz Mikuła2019-03-031-2/+1
| |
| * Upgrade bunch of EOL docker images to Ubuntu 18.04Mateusz Mikuła2019-03-039-9/+10
| |
* | Auto merge of #1296 - gnzlbg:build_uclib, r=gnzlbgbors2019-03-036-106/+134
|\ \ | | | | | | | | | Check that more targets build
| * | Fix uclibc l4regnzlbg2019-03-034-63/+74
| | |
| * | Fix uclibc build errorsgnzlbg2019-03-032-44/+53
| | |
| * | Check that more targets buildgnzlbg2019-03-031-4/+12
|/ /
* | Auto merge of #1292 - hermitcore:master, r=gnzlbgbors2019-03-036-61/+412
|\ \ | | | | | | | | | | | | | | | add HermitCore support even if it doesn't have a UNIX interface Currently, we redefine the interface between the HermitCore kernel (https://hermitcore.org) and Rust’s standard library. In the future, it will not depend on a POSIX-compatible C library. Consequently, we add the support of HermitCore if the "unix" environment isn’t set. It will be great to integrate this patch because it would simplify our development. The classical interface is still supported and part of the subdirectory "unix".
| * | remove obsolete definition of gid_t and uid_tStefan Lankes2019-03-031-2/+0
| | |
| * | remove unused variablesStefan Lankes2019-03-031-4/+2
| | |
| * | add missing debug trait for sockaddr_storageStefan Lankes2019-03-031-3/+43
| | |
| * | add missing traits like DebugStefan Lankes2019-03-031-59/+280
| | |
| * | allowd unused types ggid_t and uuid_tStefan Lankes2019-03-031-0/+2
| | |
| * | add target "hermit" to build.shStefan Lankes2019-03-031-0/+2
| | |
| * | remove redefinition of c_char and w_char, remove typoStefan Lankes2019-03-022-3/+1
| | |
| * | Merge remote-tracking branch 'rustlang/master'Stefan Lankes2019-03-0273-1793/+5331
| |\ \
| * | | add HermitCore support even if it doesn't have a UNIX interfaceStefan Lankes2019-03-024-0/+92
| | | |
* | | | Auto merge of #1293 - humenda:master, r=gnzlbgbors2019-03-033-13/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | x86_64-uclibc-l4re: fix syntax error + linter issues - fix syntax error in expand_align macro - fix errors due to doubly defined symbols / functions for x86_64-uclibc
| * | | | fix style issueSebastian Humenda2019-03-022-2/+1
| | | | |
| * | | | x86_64-uclibc-l4re: fix syntax error + linter issuesSebastian Humenda2019-03-022-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - fix syntax error in expand_align macro - fix errors due to doubly defined symbols / functions for x86_64-uclibc
* | | | | Auto merge of #1295 - semarie:openbsd-vm_size_t, r=gnzlbgbors2019-03-034-1/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vm_size_t does not exist on OpenBSD and Bitrig unbreak openbsd and bitrig after #1294 r? @gnzlbg
| * | | | | vm_size_t does not exist on OpenBSDSébastien Marie2019-03-034-1/+3
|/ / / / /
* | | | | Auto merge of #1294 - GuillaumeGomez:vm-size-t, r=gnzlbgbors2019-03-031-0/+1
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | Add vm_size_t
| * | | | Add vm_size_tGuillaume Gomez2019-03-031-0/+1
|/ / / /
* | | | Auto merge of #1291 - semarie:openbsd-pthread-stack-min, r=gnzlbgbors2019-03-024-3/+3
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | adjust PTHREAD_STACK_MIN to current value on OpenBSD adjust `PTHREAD_STACK_MIN` to current value on OpenBSD, and while here, generate the right file in test_openbsd() I should say that I am a bit disappointed. If I didn't miss anything, the related change for `PTHREAD_STACK_MIN` is near to one year old. And clearly with the name error in `test_openbsd()` something wasn't clean.
| * | | adjust PTHREAD_STACK_MIN to current value on OpenBSDSébastien Marie2019-03-024-3/+3
| | | | | | | | | | | | | | | | while here, generate the right file in test_openbsd()
* | | | Auto merge of #1290 - gnzlbg:doc_link, r=gnzlbgbors2019-03-021-0/+4
|\ \ \ \ | |/ / / |/| | | | | | | Link docs for other platforms in docs.rs
| * | | Link docs for other platforms in docs.rsgnzlbg2019-03-021-0/+4
| | | |
* | | | Auto merge of #1154 - gnzlbg:semverver2, r=gnzlbgbors2019-03-022-0/+82
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Verify that only non-technical breaking changes are applied to libc Closes #270 . cc @alexcrichton so this would be a solution to #270 that uses rust-semverver to check that the API of `libc` contains only non-technical breaking changes. This is a WIP and uses a fork of `rust-semverver` for now, but I've sent PRs upstream already. This is the only idea I have for solving #270 . `rust-semverver` is not perfect, but it can deal with functions, consts, and simple structs just fine, and that's pretty much everything that libc uses. cc @ibabushkin Some other notes: * we have to compile `rust-semverver` for each toolchain version, and it depends on `cargo` so we have to build ~160 dependencies. Using `cache: cargo` breaks everything.
| * | | | Use semverver upstreamgnzlbg2019-03-011-8/+2
| | | | |
| * | | | Allow the Semver jobs to failgnzlbg2019-02-261-2/+4
| | | | |
| * | | | Test semver for all normal targetsgnzlbg2019-02-262-7/+86
| | | | |
View Lorry Controller Status