From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Aleksandar Rikalo <arikalo@gmail.com>,
Riku Voipio <riku.voipio@iki.fi>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <richard.henderson@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/5] docker: Remove 32-bit MIPS toolchain from debian-all-test image
Date: Fri, 22 Aug 2025 12:23:07 +0100 [thread overview]
Message-ID: <87ect3k3c4.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250820142108.46639-2-philmd@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Wed, 20 Aug 2025 16:21:04 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> In commit d3322023bfe ("configure: unify again the case arms in
> probe_target_compiler") we lost coverage of 32-bit MIPS with the
> debian-all-test image. No need to keep installing the toolchain.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> tests/docker/dockerfiles/debian-all-test-cross.docker | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/tests/docker/dockerfiles/debian-all-test-cross.docker b/tests/docker/dockerfiles/debian-all-test-cross.docker
> index 420a4e33e60..bc74d65a634 100644
> --- a/tests/docker/dockerfiles/debian-all-test-cross.docker
> +++ b/tests/docker/dockerfiles/debian-all-test-cross.docker
> @@ -40,14 +40,10 @@ ENV AVAILABLE_COMPILERS gcc-aarch64-linux-gnu \
> libc6-dev-arm64-cross \
> gcc-arm-linux-gnueabihf \
> libc6-dev-armhf-cross \
> - gcc-mips-linux-gnu \
> - libc6-dev-mips-cross \
> gcc-mips64-linux-gnuabi64 \
> libc6-dev-mips64-cross \
> gcc-mips64el-linux-gnuabi64 \
> libc6-dev-mips64el-cross \
> - gcc-mipsel-linux-gnu \
> - libc6-dev-mipsel-cross \
> gcc-powerpc64le-linux-gnu \
> libc6-dev-ppc64el-cross \
> gcc-riscv64-linux-gnu \
You also need to remove the references in configure:
hppa|m68k|mips|riscv64|sparc64)
container_image=debian-all-test-cross
;;
mips64)
container_image=debian-all-test-cross
container_cross_prefix=mips64-linux-gnuabi64-
;;
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-08-22 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 14:21 [PATCH 0/5] tcg/mips: Remove support for 32-bit hosts Philippe Mathieu-Daudé
2025-08-20 14:21 ` [PATCH 1/5] docker: Remove 32-bit MIPS toolchain from debian-all-test image Philippe Mathieu-Daudé
2025-08-22 11:23 ` Alex Bennée [this message]
2025-08-22 14:49 ` Philippe Mathieu-Daudé
2025-08-20 14:21 ` [PATCH 2/5] gitlab: Stop cross-testing for 32-bit MIPS hosts Philippe Mathieu-Daudé
2025-08-25 12:31 ` Thomas Huth
2025-08-20 14:21 ` [PATCH 3/5] docker: Stop building 32-bit MIPS images Philippe Mathieu-Daudé
2025-08-25 12:33 ` Thomas Huth
2025-08-20 14:21 ` [PATCH 4/5] tcg/mips: Check O32/N32/64 ABI definitions actually exist Philippe Mathieu-Daudé
2025-08-21 21:09 ` Richard Henderson
2025-08-20 14:21 ` [PATCH 5/5] tcg/mips: Remove support for 32-bit hosts Philippe Mathieu-Daudé
2025-08-21 20:48 ` [PATCH 0/5] " Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ect3k3c4.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=arikalo@gmail.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=riku.voipio@iki.fi \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).