From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/7] Revert "ci: container: downgrade OpenRISC toolchain from 14.2.0 to 13.1.0"
Date: Wed, 26 Mar 2025 13:36:13 +0100 [thread overview]
Message-ID: <20250326123619.282897-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250326123619.282897-1-a.fatoum@pengutronix.de>
This or1k issue turned out to be caused by the QEMU update[1] that came
with bumping the Debian release of the container image and not the
toolchain update.
We don't have the QEMU fix in the container yet, but we have a
workaround in commit b2a21df3b07b ("openrisc: dts: describe all 4 UARTs").
So let's revert the erroneous toolchain downgrade.
[1]: https://lore.kernel.org/all/20241203111513.402641-2-shorne@gmail.com/
Fixes: 6d4c6b01f4c4 ("ci: container: downgrade OpenRISC toolchain from 14.2.0 to 13.1.0")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
test/Containerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/Containerfile b/test/Containerfile
index 53a5443e48fe..94b3f618261c 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -61,7 +61,7 @@ RUN korg_crosstool_dl() { wget -nv -O - https://mirrors.edge.kernel.org/pub/tool
korg_crosstool_dl x86_64 ${GCC_VERSION} arm-linux-gnueabi && \
korg_crosstool_dl x86_64 ${GCC_VERSION} aarch64-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} mips-linux && \
- korg_crosstool_dl x86_64 13.1.0 or1k-linux && \
+ korg_crosstool_dl x86_64 ${GCC_VERSION} or1k-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} powerpc-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} riscv64-linux
--
2.39.5
next prev parent reply other threads:[~2025-03-26 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 12:36 [PATCH 0/7] ci: container: include musl and LLVM Ahmad Fatoum
2025-03-26 12:36 ` Ahmad Fatoum [this message]
2025-03-26 12:36 ` [PATCH 2/7] ci: container: download and delete kvx.tgz in the same layer Ahmad Fatoum
2025-03-26 12:36 ` [PATCH 3/7] ci: container: don't leave labgrid checkout in /tmp Ahmad Fatoum
2025-03-26 12:36 ` [PATCH 4/7] ci: container: don't install recommended packages Ahmad Fatoum
2025-03-26 12:36 ` [PATCH 5/7] ci: container: run apt-get clean after installation Ahmad Fatoum
2025-03-26 12:36 ` [PATCH 6/7] ci: container: add musl-tools Ahmad Fatoum
2025-03-26 12:36 ` [PATCH 7/7] ci: container: install LLVM/clang Ahmad Fatoum
2025-03-27 9:21 ` [PATCH 0/7] ci: container: include musl and LLVM Sascha Hauer
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=20250326123619.282897-2-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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