about summary refs log tree commit diff
path: root/src/ci/docker/dist-various-1
AgeCommit message (Collapse)AuthorLines
2019-04-23Remove unnecessary ignore-tidy-linelengthvarkor-1/+0
2019-04-03Add dist builder for Armv8-M Baseline and HFHugues de Valon-0/+2
This commit adds the Armv8-M Baseline and Armv8-M Mainline with FPU targets in the list of targets that get their dist components built. It also update the build-manifest so that this target gets also its dist components uploaded.
2019-03-20Use `curl` instead of `wget` in install-x86_64-redox.shkennytm-1/+1
2019-03-17Update CI configuration for building Redox librariesJeremy Soller-8/+2
2019-02-12Add riscv64gc-unknown-none-elf targetVadim Kaushan-0/+1
2019-02-12Add riscv64imac-unknown-none-elf targetVadim Kaushan-0/+1
2019-01-29Auto merge of #57862 - hsivonen:buildneon, r=alexcrichtonbors-2/+6
Build the standard library for thumbv7neon-unknown-linux-gnueabihf in CI Using the `dist-armv7-linux` image instead of `dist-various-1` in order to use the ARMv7 toolchain available in `dist-armv7-linux`. Closes #57030.
2019-01-28Build the standard library for thumbv7neon-unknown-linux-gnueabihf in CIHenri Sivonen-2/+6
Closes #57030.
2019-01-22use port 80 for retrieving GPG keyAndy Russell-1/+1
This works around firewalls blocking port 11371. See https://unix.stackexchange.com/questions/75892/keyserver-timed-out-when-trying-to-add-a-gpg-public-key.
2019-01-09Replace Arm GCC to a more recent versionHugues de Valon-2/+8
The version included in Ubuntu 16.04 repositories in the dist-various-1 docker, Arm GCC version 4.9, does not support the new Armv8-M architecture. This commit adds the team-gcc-arm-embedded PPA to get through APT a newer version of Arm GCC.
2019-01-09Add dist builder for Armv8-M MainlineHugues de Valon-0/+1
This commit adds the Armv8-M Mainline target in the list of targets that get their dist components built. It also update the build-manifest so that this target gets also its dist components uploaded.
2018-12-25Remove licensesMark Rousskov-40/+0
2018-12-11fix rust-lang/rust issue #50583Piers Finlayson-2/+2
2018-09-30[ci] add qemu-system-arm in docker imageHideki Sekine-1/+2
2018-08-30[RISCV] Add riscv32imc-unknown-none-elf target.David Craven-0/+1
2018-08-26fix docker build for the armebv7r-none-eabi targetJorge Aparicio-1/+2
2018-08-26add armebv7r-none-eabi targetJorge Aparicio-0/+1
2018-08-26build rust-std components for the Cortex-R targetsJorge Aparicio-1/+4
2018-08-01[RISCV] Enable CI.David Craven-0/+1
2018-07-25Auto merge of #52561 - ljedrz:fixme_cc_271, r=alexcrichtonbors-7/+1
Remove obsolete armv5te vars from the dist-various-1 Dockerfile The [related cc issue](https://github.com/alexcrichton/cc-rs/issues/271) is closed and its changes are in force.
2018-07-20Remove obsolete armv5te vars from the dist-various-1 Dockerfileljedrz-7/+1
2018-07-18Re-include `thumbv6m-none-eabi` to `run-make` targetHideki Sekine-2/+2
2018-07-18Use `dist-various-1` Dockerfile.Hideki Sekine-1/+8
2018-05-04Merge armv5te musl container with dist-various-1Harm Berntsen-1/+9
2018-04-05Rollup merge of #49563 - japaric:std-thumb, r=alexcrichtonkennytm-1/+7
add a dist builder to build rust-std components for the THUMB targets the rust-std component only contains the core and compiler-builtins (+c +mem) crates cc #49382 - I'm not entirely sure if this PR alone will produce rust-std components installable by rustup or if something else needs to be changed - I could have done the THUMB builds in an existing builder / image; I wasn't sure if that was a good idea so I added a new image - I could build other crates like alloc into the rust-std component but, AFAICT, that would require calling Cargo a second time (one for alloc and one for compiler-builtins), or have alloc depend on compiler-builtins (#49503 will perform that change) *and* have alloc resurface the "c" and "mem" Cargo features. r? @alexcrichton
2018-04-03merge dist-various-3 into dist-various-1Jorge Aparicio-1/+7
2018-04-02Update sccache to its master branchAlex Crichton-0/+8
Ideally I'd like to soon enable sccache for rustbuild itself and some of the stage0 tools, but for that to work we'll need some better Rust support than the pretty old version we were previously using!
2018-03-25rustbuild: Disable docs on cross-compiled buildsAlex Crichton-1/+2
This commit disables building documentation on cross-compiled compilers, for example ARM/MIPS/PowerPC/etc. Currently I believe we're not getting much use out of these documentation artifacts and they often take 10-15 minutes total to build as it requires building rustdoc/rustbook and then also generating all the documentation, especially for the reference and the book itself. In an effort to cut down on the amount of work that we're doing on dist CI builders in light of recent timeouts this was some relatively low hanging fruit to cut which in theory won't have much impact on the ecosystem in the hopes that the documentation isn't used too heavily anyway. While initial analysis in #48827 showed only shaving 5 minutes off local builds the same 5 minute conclusion was drawn from #48826 which ended up having nearly a half-hour impact on the bots. In that sense I'm hoping that we can land this and test out what happens on CI to see how it affects timing. Note that all tier 1 platforms, Windows, Mac, and Linux, will continue to generate documentation.
2018-03-02Remove --host and --target arguments to configureMark Simulacrum-1/+0
These arguments are passed to the relevant x.py invocation in all cases anyway. As such, there is no need to separately configure them. x.py will ignore the configuration when they are passed on the command line anyway.
2018-01-28rustc: Split Emscripten to a separate codegen backendAlex Crichton-1/+2
This commit introduces a separately compiled backend for Emscripten, avoiding compiling the `JSBackend` target in the main LLVM codegen backend. This builds on the foundation provided by #47671 to create a new codegen backend dedicated solely to Emscripten, removing the `JSBackend` of the main codegen backend in the process. A new field was added to each target for this commit which specifies the backend to use for translation, the default being `llvm` which is the main backend that we use. The Emscripten targets specify an `emscripten` backend instead of the main `llvm` one. There's a whole bunch of consequences of this change, but I'll try to enumerate them here: * A *second* LLVM submodule was added in this commit. The main LLVM submodule will soon start to drift from the Emscripten submodule, but currently they're both at the same revision. * Logic was added to rustbuild to *not* build the Emscripten backend by default. This is gated behind a `--enable-emscripten` flag to the configure script. By default users should neither check out the emscripten submodule nor compile it. * The `init_repo.sh` script was updated to fetch the Emscripten submodule from GitHub the same way we do the main LLVM submodule (a tarball fetch). * The Emscripten backend, turned off by default, is still turned on for a number of targets on CI. We'll only be shipping an Emscripten backend with Tier 1 platforms, though. All cross-compiled platforms will not be receiving an Emscripten backend yet. This commit means that when you download the `rustc` package in Rustup for Tier 1 platforms you'll be receiving two trans backends, one for Emscripten and one that's the general LLVM backend. If you never compile for Emscripten you'll never use the Emscripten backend, so we may update this one day to only download the Emscripten backend when you add the Emscripten target. For now though it's just an extra 10MB gzip'd. Closes #46819
2018-01-23Build musl with -fPIC for all targetsMarco A L Barbosa-1/+0
2018-01-22Do not assume dynamic linking for musl/mips[el] targetsMarco A L Barbosa-10/+21
All musl targets except mips[el] assume static linking by default. This can be confusing https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084 When the musl/mips[el] targets was [added](https://github.com/rust-lang/rust/pull/31298), dynamic linking was chosen because of binary size concerns, and probably also because libunwind [didn't](https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084/8) supported mips. Now that we have `crt-static` target-feature (the user can choose dynamic link for musl targets), and libunwind [6.0](https://github.com/llvm-mirror/libunwind/commits/release_60) add support to mips, we do not need to assume dynamic linking.
2018-01-03ci: use musl shared script in dist-various-1 (for arm targets)Marco A L Barbosa-160/+29
Update libunwind to 39. This is necessary to build the arm targets
2017-12-26Add dist builder for armv5te-unknown-linux-gnueabiMarco A L Barbosa-1/+6
2017-12-11Remove armv5te target from dist-various-1Marco A L Barbosa-6/+1
Reverts https://github.com/rust-lang/rust/pull/46498 I must have made some mistake when I tested that commit and thought armv5te target worked. but testing it now the produced binaries segfaults (https://github.com/rust-lang/rust/pull/46498#issuecomment-350599233). I tried using crosstool-ng and buildroot toolchain (for armv5te) but the produced binaries also segfaults. Maybe there is a issue with the target, but I cannot investigate it any further. I think the best for now is not to distribute the armv5te target. I'm sorry for what happened.
2017-12-05Add armv5te-unknown-linux-gnueabi to cross builderMarco A L Barbosa-1/+6
2017-12-04Rename cross(2) builder to dist-various-{1,2}Marco A L Barbosa-0/+329
Follows the convention of the other builders.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-24 12:29:16 +0000