rust/src/ci/docker/scripts, branch perf-tmp

CI: rfl: move job forward to Linux v6.17-rc5 to remove temporary commits

2025-09-09T07:35:07+00:00

v6.17-rc5 contains the equivalent of the two commits we had here, thus move the Rust for Linux job forward to that so that we don't need the temporary commits anymore. Signed-off-by: Miguel Ojeda

CI: rfl: move job forward to Linux v6.17-rc3 plus 2 commits

2025-09-03T09:02:23+00:00

This upgrades the Rust CI from v6.16-rc1 plus a temporary commit for the >= 1.91 target spec [1] to v6.17-rc3 with two commits pending to be merged upstream -- one for the same target spec format change [1] and another for the `file_as_c_str` change [2]. Link: https://github.com/rust-lang/rust/pull/144443 [1] Link: https://github.com/rust-lang/rust/pull/145928 [2] Signed-off-by: Miguel Ojeda

CI: rfl: support Rust >= 1.91.0 target spec

2025-08-27T21:44:49+00:00

To unblock the Rust CI in PR [1], use a temporary commit from Rust for Linux that supports the future target spec format. Link: https://github.com/rust-lang/rust/pull/144443 [1] Signed-off-by: Miguel Ojeda

Use ci-mirrors for binutils in freebsd-toolchain.sh

2025-08-13T12:25:53+00:00

Use runtimes build for host compiler-rt build

2025-08-05T13:43:51+00:00

The project build for compiler-rt is deprecated. The runtimes build will use the just-built clang. As such, we also need to pass --gcc-toolchain to the runtimes build, so that it can find the GCC installation.

Update host toolchain

2025-08-01T08:18:28+00:00

Necessary to avoid a bolt-related crash.

Fix handling of SCRIPT_ARG in docker images

2025-07-15T14:23:15+00:00

Instead of making this a build parameter, pass the SCRIPT as an environment variable. To this purpose, normalize on always referring to a script in `/scripts`. For i686-gnu-nopt-2 I had to create a separate script, because Docker seems to be really terrible at command line argument parsing, so it's not possible to pass an environment variable that contains whitespace.

Get rid of build-powerpc64le-toolchain.sh

2025-07-04T08:46:12+00:00

The dist-powerpc64le-linux-musl runner never actually used the toolchain that the script produced, it instead used the one from crosstool-ng. The dist-powerpc64le-linux-gnu runner did use it, from what I can tell mainly to get a glibc 2.17 version with ppc64le support backported. Since crosstool-ng has the necessary patches, we can just use crosstool-ng to get an appropriate toolchain. While at it, use kernel 3.10 headers since that's the version documented in platform support for this target. Signed-off-by: Jens Reidel

Remove `build --stage 0` from CI scripts

2025-06-23T08:11:01+00:00

CI: rfl: move job forward to Linux v6.16-rc1

2025-06-08T19:37:37+00:00

Remove the comment on top as well, since that issue is now fixed in this new tag. Signed-off-by: Miguel Ojeda