<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/ci/docker/dist-armv7-linux/Dockerfile, branch 1.45.2</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.45.2</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.45.2'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2020-04-23T19:45:18+00:00</updated>
<entry>
<title>Enable "full tools" option on ARM dist builders</title>
<updated>2020-04-23T19:45:18+00:00</updated>
<author>
<name>Alex Crichton</name>
<email>alex@alexcrichton.com</email>
</author>
<published>2020-04-23T19:40:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c7a7658c6dd89fd5e0a696460fe9abceb2bde8aa'/>
<id>urn:sha1:c7a7658c6dd89fd5e0a696460fe9abceb2bde8aa</id>
<content type='text'>
This commit switches the `--enable-extended` option on the arm-related
dist builders to `--enable-full-tools`. This alias in `config.py`
corresponds to enabling a few more options:

* `rust.lld = true` - this is the main purpose of this PR, to enable LLD
  on ARM-related platforms. This means it will effectively unlock
  compilation of wasm programs from an arm host.

* `rust.llvm-tools = true` - it turns out that this option is largely
  ignored in rustbuild today. This is only read in one location to set
  some flags for the `llvm-tools` package, but the `llvm-tools` package
  is already produced on all of these builders. It's predicted that this
  will have no effect on build times.

* `rust.codegen-backends = ['llvm']` - historically this also enabled
  the emscripten backend, but that has long since been removed.

This brings the ARM dist builders in line with the x86_64 dist builders
using this flag. The hope is that the extra time spent on CI building
LLD will acceptable because it's cached by `sccache`, LLD is a
relatively small C++ project, and the dist builders are all clocking
well under 3 hours (the slowest of all builders) around 2 hours.

There's likely some possible cleanup that can happen with these
configure options since it doesn't look like they've aged too too well,
but I'm hopeful that possible refactorings, if necessary, could be
deferred to future PRs.
</content>
</entry>
<entry>
<title>Enforce Python 3 as much as possible</title>
<updated>2020-04-10T13:09:58+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume1.gomez@gmail.com</email>
</author>
<published>2019-11-21T12:57:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=38eb369fa4d06e55869a8fae62796a7b0085a5bd'/>
<id>urn:sha1:38eb369fa4d06e55869a8fae62796a7b0085a5bd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Deduplicate crosstool-ng.sh</title>
<updated>2020-03-31T00:09:45+00:00</updated>
<author>
<name>Ben Wolsieffer</name>
<email>benwolsieffer@gmail.com</email>
</author>
<published>2020-03-31T00:09:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=55bdb61b48a01e9a7c6efb4622fecab2411c0287'/>
<id>urn:sha1:55bdb61b48a01e9a7c6efb4622fecab2411c0287</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix path to crosstool-ng.sh</title>
<updated>2019-10-13T07:06:25+00:00</updated>
<author>
<name>qtmlabs</name>
<email>qtmlabs@protonmail.com</email>
</author>
<published>2019-10-13T07:06:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e58ad8dedfd2befc601363e5f4930e45b201f686'/>
<id>urn:sha1:e58ad8dedfd2befc601363e5f4930e45b201f686</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Upgrade GCC to 8.3.0, glibc to 1.17.0 and crosstool-ng to 1.24.0 for dist-armv7-linux</title>
<updated>2019-10-11T08:13:22+00:00</updated>
<author>
<name>qtmlabs</name>
<email>qtmlabs@protonmail.com</email>
</author>
<published>2019-10-11T08:13:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=90d0baf2b4ec7837b50f1d57ff79e31dbebf10c6'/>
<id>urn:sha1:90d0baf2b4ec7837b50f1d57ff79e31dbebf10c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[CI] Update crosstool-ng builders to GCC 5.2</title>
<updated>2019-02-12T17:56:09+00:00</updated>
<author>
<name>Josh Stone</name>
<email>jistone@redhat.com</email>
</author>
<published>2019-02-12T17:56:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e0544ca1cff6492ac40c405e04f0c23666536b3b'/>
<id>urn:sha1:e0544ca1cff6492ac40c405e04f0c23666536b3b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rustbuild: Disable docs on cross-compiled builds</title>
<updated>2018-03-26T06:31:41+00:00</updated>
<author>
<name>Alex Crichton</name>
<email>alex@alexcrichton.com</email>
</author>
<published>2018-03-19T17:58:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=bd286413443c31c99330358967fb0159de8a3589'/>
<id>urn:sha1:bd286413443c31c99330358967fb0159de8a3589</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Remove --host and --target arguments to configure</title>
<updated>2018-03-02T18:28:29+00:00</updated>
<author>
<name>Mark Simulacrum</name>
<email>mark.simulacrum@gmail.com</email>
</author>
<published>2018-02-11T22:52:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=ab7ce1c3c48d4f1be6c16928704e2eec0aed9ae2'/>
<id>urn:sha1:ab7ce1c3c48d4f1be6c16928704e2eec0aed9ae2</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>ci: Remove the need for `dumb-init`</title>
<updated>2017-08-27T01:34:13+00:00</updated>
<author>
<name>Alex Crichton</name>
<email>alex@alexcrichton.com</email>
</author>
<published>2017-08-27T01:34:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=ffe64a26abb194a7ddcc5f410512043a65b3eb91'/>
<id>urn:sha1:ffe64a26abb194a7ddcc5f410512043a65b3eb91</id>
<content type='text'>
Newer versions of Docker have a `--init` argument which spawns an init process
in the container, which we should be able to use everywhere now.
</content>
</entry>
<entry>
<title>Updated docker images to factor out common scripts</title>
<updated>2017-07-13T01:25:36+00:00</updated>
<author>
<name>Ty Coghlan</name>
<email>Coghlan.Ty@gmail.com</email>
</author>
<published>2017-07-09T15:01:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=250346128b0083c8137171af503bda194c6124dd'/>
<id>urn:sha1:250346128b0083c8137171af503bda194c6124dd</id>
<content type='text'>
</content>
</entry>
</feed>
