diff options
| author | bors <bors@rust-lang.org> | 2017-01-29 21:28:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-01-29 21:28:28 +0000 |
| commit | d01e22e53f7495499864c371e13e422611b8c377 (patch) | |
| tree | 255095c028033ec754df0b2c066baa6cc74cbfe0 /src/test/incremental/thinlto | |
| parent | 4be49e1937e25cc9c78d7758e095046563052dec (diff) | |
| parent | cb47d9ffc3a4fcd66e38b9065bcb9a9487dea3fc (diff) | |
| download | rust-d01e22e53f7495499864c371e13e422611b8c377.tar.gz rust-d01e22e53f7495499864c371e13e422611b8c377.zip | |
Auto merge of #39382 - cuviper:ibm-rewind, r=alexcrichton
travis: move IBM backwards in time Using Ubuntu's cross-toolchains for powerpc* and s390x meant they were depending on glibc symbols from Ubuntu 16.04. And if that host is ever updated to a new release, the toolchains would raise the bar too. This switches powerpc, powerpc64, and s390x to use crosstool-ng toolchains, configured approximately like RHEL6 with kernel 2.6.32 and glibc 2.12. This ABI level should also be compatible with Debian 7 (wheezy) and Ubuntu 12.04 (precise). For powerpc64le, the challenge was that only glibc-2.19 officially added support, but RHEL7 backported those changes to glibc-2.17. The backport patches are complex and numerous, so instead of trying to push those into crosstool-ng, this just uses glibc binaries directly from CentOS 7 and builds the toolchain manually. This is ported from rust-lang/rust-buildbot#149. r? @alexcrichton
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions