From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Yann Sionneau <ysionneau@kalrayinc.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/6] ci: container: add kvx-elf- toolchain
Date: Mon, 12 Aug 2024 11:15:18 +0200 [thread overview]
Message-ID: <20240812091522.3035469-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240812091522.3035469-1-a.fatoum@pengutronix.de>
ARCH=kvx build has been broken in the past, because it was the only
barebox platform that wasn't build tested.
There are prebuilt toolchains of acceptable footprint (64M compressed),
so let's integrate them into the image, so we can add it to build test.
There's no prebuilt Qemu unfortunately, so actually testing the result
will have to wait.
Cc: Yann Sionneau <ysionneau@kalrayinc.com>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
test/Containerfile | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/test/Containerfile b/test/Containerfile
index 06d155bf4d28..2f8c969d824f 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -60,6 +60,13 @@ RUN korg_crosstool_dl() { wget -nv -O - https://mirrors.edge.kernel.org/pub/tool
korg_crosstool_dl x86_64 ${GCC_VERSION} powerpc-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} riscv64-linux
+RUN wget -O kvx.tgz https://github.com/kalray/build-scripts/releases/download/v5.0.0/gcc-kalray-kvx-ubuntu-22.04-v5.0.0.tar.gz
+
+RUN echo "d27b3d6e6246f5debffee0bb01e77eb133bd32c658782a68a779cf9fb4c436bc kvx.tgz" | \
+ sha256sum --check --status
+
+RUN tar -C /opt -xzf kvx.tgz && rm kvx.tgz
+
RUN wget "https://github.com/qemu/qemu/blob/v5.2.0/pc-bios/opensbi-riscv32-generic-fw_dynamic.bin?raw=true" -O /usr/share/qemu/opensbi-riscv32-generic-fw_dynamic.bin
# Create our user/group
@@ -79,5 +86,6 @@ ENV CROSS_COMPILE_mips=/opt/gcc-${GCC_VERSION}-nolibc/mips-linux/bin/mips-linux-
ENV CROSS_COMPILE_openrisc=/opt/gcc-${GCC_VERSION}-nolibc/or1k-linux/bin/or1k-linux-
ENV CROSS_COMPILE_powerpc=/opt/gcc-${GCC_VERSION}-nolibc/powerpc-linux/bin/powerpc-linux-
ENV CROSS_COMPILE_riscv=/opt/gcc-${GCC_VERSION}-nolibc/riscv64-linux/bin/riscv64-linux-
+ENV CROSS_COMPILE_kvx=/opt/gcc-kalray-kvx-v5.0.0/bin/kvx-elf-
USER barebox:barebox
--
2.39.2
next prev parent reply other threads:[~2024-08-12 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 9:15 [PATCH 1/6] ci: container: update to Debian Bookworm with GCC v14.2.0 Ahmad Fatoum
2024-08-12 9:15 ` Ahmad Fatoum [this message]
2024-08-12 9:29 ` [PATCH 2/6] ci: container: add kvx-elf- toolchain Yann Sionneau
2024-08-12 9:15 ` [PATCH 3/6] ci: container: update to newer Labgrid Ahmad Fatoum
2024-08-12 12:52 ` Yann Sionneau
2024-08-12 13:30 ` Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 4/6] test: sandbox: support testing with Labgrid Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 5/6] ci: pytest: test sandbox configuration with labgrid Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 6/6] ci: build: add kvx build test Ahmad Fatoum
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=20240812091522.3035469-2-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ysionneau@kalrayinc.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