about summary refs log tree commit diff
path: root/src/ci/docker/scripts
AgeCommit message (Collapse)AuthorLines
2019-10-20Auto merge of #65302 - msizanoen1:fix-armv7-segfault, r=alexcrichtonbors-0/+1
Upgrade GCC to 8.3.0, glibc to 1.17.0 and crosstool-ng to 1.24.0 for dist-armv7-linux #62896 was caused by the usage of the GCC 5.2.0 toolchain, which was released back in 2015 and may have bugs affecting LLVM 9. This PR upgrade GCC to 8.3.0 from 5.2.0, glibc from 1.16.0 to 1.17.0 and crosstool-ng to 1.24.0 only for dist-armv7-linux. Fixes #62896 r? @alexcrichton
2019-10-16User should not change between emcc install and useThomas Lively-10/+0
2019-10-16Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-45/+3
- Compatible with Emscripten 1.38.46-upstream or later upstream. - Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the old incorrect wasm32 C call ABI with the correct one, preserving the old one as wasm32_bindgen_compat for wasm-bindgen compatibility. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Uses EMCC_CFLAGS on CI to avoid the timeout problems with #63649.
2019-10-12Add crosstool-ng 1.24.0 unzip dependencyqtmlabs-0/+1
2019-10-05Revert "Auto merge of #63649 - tlively:emscripten-upstream-upgrade, ↵Tyler Mandry-3/+45
r=alexcrichton" This reverts commit 7870050796e5904a0fc85ecbe6fa6dde1cfe0c91, reversing changes made to 2e7244807a7878f6eca3eb7d97ae9b413aa49014.
2019-10-04Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-45/+3
- Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the incorrect wasm32 C call ABI with the old asmjs version, which is correct for both wasm32 and JS. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Temporarily makes Emscripten targets use panic=abort by default because supporting unwinding will require an LLVM patch.
2019-08-15Use libunwind from llvm-project submodule for musl targetsMarco A L Barbosa-50/+2
2019-08-12ci: move mirrors to their standalone bucketPietro Albini-5/+7
Currently mirrors are stored in the rust-lang-ci2 S3 bucket along with CI toolchains. This is problematic for multiple reasons: - CI IAM credentials are allowed to both edit and delete those files. A malicious user gaining access to those credentials would be able to change our mirrored dependencies, possibly backdooring the compiler. - Contents of the rust-lang-ci2 bucket are disposable except for the mirrors' content. When we implement backups for S3 buckets we'd have to replicate just that part of the bucket, complicating the backup logic and increasing the chance of mistakes. A standalone bucket will be way easier to backup. This commit switches our CI to use the new rust-lang-ci-mirrors bucket.
2019-06-30Auto merge of #61252 - indygreg:upgrade-musl, r=alexcrichtonbors-1/+1
Update musl to 1.1.22 This is the latest available version. I noticed Rust wasn't using the latest version when I attempted to have Cargo link object files produced outside of Cargo / Rust's toolchain and was getting missing symbol errors. Those missing symbols were added in 1.1.21 and 1.1.22. I'm not fully sure of the implications of this change or how comprehensive the test coverage is. Upstream changes in 1.1.21 and 1.1.22 can be found at https://git.musl-libc.org/cgit/musl/tree/WHATSNEW?h=v1.1.22&id=e97681d6f2c44bf5fa9ecdd30607cb63c780062e#n1989.
2019-05-31Auto merge of #61300 - indygreg:upgrade-cross-make, r=sanxiynbors-2/+2
Update musl-cross-make to 0.9.8 This version uses musl 1.1.22 and GCC 6.4.0 by default. It also contains support for newer binutils and GCC versions, should we want to bump those as well. But I'm purposefully limiting this patch in order to reduce the surface area for controversy.
2019-05-29Update all s3 URLs used on CI with subdomainsAlex Crichton-3/+3
Ensure that they're all forwards-compatible with AWS updates happening next year by ensuring the bucket name shows up in the domain name. Closes #61168
2019-05-28Update musl-cross-make to 0.9.8Gregory Szorc-2/+2
This version uses musl 1.1.22 and GCC 6.4.0 by default. It also contains support for newer binutils and GCC versions, should we want to bump those as well. But I'm purposefully limiting this patch in order to reduce the surface area for controversy.
2019-05-28Update musl to 1.1.22.Gregory Szorc-1/+1
This is the latest available version. I noticed Rust wasn't using the latest version when I attempted to have Cargo link object files produced outside of Cargo / Rust's toolchain and was getting missing symbol errors. Those missing symbols were added in 1.1.21 and 1.1.22. I'm not fully sure of the implications of this change or how comprehensive the test coverage is. Upstream changes in 1.1.21 and 1.1.22 can be found at https://git.musl-libc.org/cgit/musl/tree/WHATSNEW?h=v1.1.22&id=e97681d6f2c44bf5fa9ecdd30607cb63c780062e#n1989.
2019-05-10Conditionally provide cc in musl-toolchain.shMateusz Mikuła-6/+8
2019-05-10Make tests compatible with musl hostMateusz Mikuła-0/+7
2019-04-27tidy: Fix false positives from long URLsVadim Petrochenkov-2/+0
2019-04-22Remove double trailing newlinesvarkor-2/+0
2019-04-12ci: use a custom android sdk manager with pinning and mirroringPietro Albini-59/+211
2019-04-07ci: pin android emulator to 28.0.23Pietro Albini-2/+14
2019-04-04ci: Update FreeBSD tarball downloadsAlex Crichton-1/+5
These appear to have disappeared from the original server, so I acquired the contents from a different mirror and uploaded them to our S3 bucket
2019-03-27musl: build toolchain libs with -fPICMateusz Mikuła-0/+4
2019-03-15Fix TARGET variable in musl-toolchain.shMateusz Mikuła-1/+1
2019-03-14Address final reviewMateusz Mikuła-0/+6
2019-03-13Final cleanupsMateusz Mikuła-6/+4
2019-03-13Drop copyright notice from musl-toolchainMateusz Mikuła-10/+0
2019-03-13musl: update LLVM to 7Mateusz Mikuła-1/+1
2019-03-13Address review commentsMartell Malone-2/+2
2019-03-13musl-toolchain: fix global lib paths (dont create /lib/libc.so)Jonathan Sieber-2/+1
2019-03-13Make the musl dynamic loader known to the system, so it can execute target ↵Jonathan Sieber-0/+11
binaries
2019-03-13build a proper c++-enabled musl toolchain with musl-cross-makeJonathan Sieber-0/+66
2019-01-23make sure to accept all android licensesPietro Albini-1/+1
2018-12-25Remove licensesMark Rousskov-139/+0
2018-11-14Update CI-clang to 7.0.0 for Linux dists.Michael Woerister-1/+1
2018-11-08Update the disabled wasm32 DockerfileNikita Popov-5/+0
2018-11-04Update llvm-emscriptenNikita Popov-2/+2
This updates emscripten to version 1.38.15, which is based on LLVM 6.0.1.
2018-09-21Update musl to 1.1.20.Adrian Budau-7/+1
2018-08-19Fix typos found by codespell.Matthias Krüger-1/+1
2018-07-05Update musl to 1.1.19 and add patch to fix tls issueMarco A L Barbosa-1/+7
2018-04-10Add --enable-debug flag to musl CI build scriptAlec Mocatta-1/+1
Building for x86_64-unknown-linux-musl currently results in an executable lacking debug information for musl libc itself. If you request a backtrace in GDB while control flow is within musl – including sycalls made by musl – the result looks like: #0 0x0000000000434b46 in __cp_end () #1 0x0000000000432dbd in __syscall_cp_c () #2 0x0000000000000000 in ?? () i.e. not very helpful. Adding --enable-debug resolves this, and --enable-optimize re-enables optimisations which default to off given the previous flag.
2018-04-02Update sccache to its master branchAlex Crichton-1/+1
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-01-27Remove musl/libunwind patch for i686Marco A L Barbosa-31/+0
The i686 problem was fixed upstream: https://github.com/llvm-mirror/libunwind/commit/aa805e415f19f50ebc6f5e1e1e4bf9bb7f61816b
2018-01-23Build musl with -fPIC for all targetsMarco A L Barbosa-0/+2
2018-01-23Use libuwind 6.0 for all musl targetsMarco A L Barbosa-9/+1
2018-01-22Do not assume dynamic linking for musl/mips[el] targetsMarco A L Barbosa-1/+10
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-13Rollup merge of #47283 - malbarbo:musl-1.1.18, r=alexcrichtonkennytm-1/+1
Update musl to 1.1.18 According to http://www.musl-libc.org/download.html: This release corrects regressions in glob() and armv4t build failure introduced in the previous release, and includes an important bug fix for posix_spawnp in the presence of a large PATH environment variable.
2018-01-11Add i586-unknown-linux-musl targetMarco A L Barbosa-1/+1
2018-01-08Update musl to 1.1.18Marco A L Barbosa-1/+1
According to http://www.musl-libc.org/download.html: This release corrects regressions in glob() and armv4t build failure introduced in the previous release, and includes an important bug fix for posix_spawnp in the presence of a large PATH environment variable.
2018-01-03ci: use musl shared script in dist-i586-gnu-i686-muslMarco A L Barbosa-1/+36
2018-01-03ci: use musl shared script in dist-various-1 (for arm targets)Marco A L Barbosa-11/+37
Update libunwind to 39. This is necessary to build the arm targets
2018-01-03ci: use musl shared script in dist-x86_64-muslMarco A L Barbosa-0/+41
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-13 09:30:43 +0000