From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] ci: build: have CI build ARCH=openrisc
Date: Mon, 19 Jun 2023 11:46:37 +0200 [thread overview]
Message-ID: <20230619094637.4134449-1-a.fatoum@pengutronix.de> (raw)
qemu-system-misc ships with qemu-system-or1k and kernel.org mirrors a
crostool toolchain capable of building barebox for running in it.
Let's make use of that. We don't yet activate openrisc for CI test
as it fails to boot up with SELFTEST_OF_MANIPULATION. A suggested fix
is still under discussion[1].
[1]: https://lore.barebox.org/barebox/20230605063719.1431079-1-a.fatoum@pengutronix.de/
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.github/workflows/build-defconfigs.yml | 2 +-
test/Containerfile | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/build-defconfigs.yml b/.github/workflows/build-defconfigs.yml
index ff9264721d87..4cf6df52d44d 100644
--- a/.github/workflows/build-defconfigs.yml
+++ b/.github/workflows/build-defconfigs.yml
@@ -3,7 +3,7 @@ name: build images
on: [push, pull_request]
env:
- ARCH: arm mips powerpc riscv sandbox x86
+ ARCH: arm mips powerpc riscv sandbox x86 openrisc
jobs:
defconfigs:
diff --git a/test/Containerfile b/test/Containerfile
index a53c00584f68..224ea2ea4804 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -55,6 +55,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 ${GCC_VERSION} or1k-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} powerpc-linux && \
korg_crosstool_dl x86_64 ${GCC_VERSION} riscv64-linux
@@ -74,6 +75,7 @@ RUN cd /tmp && \
ENV CROSS_COMPILE_arm=/opt/gcc-${GCC_VERSION}-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-
ENV CROSS_COMPILE_arm64=/opt/gcc-${GCC_VERSION}-nolibc/aarch64-linux/bin/aarch64-linux-
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-
--
2.39.2
next reply other threads:[~2023-06-19 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:46 Ahmad Fatoum [this message]
2023-06-21 7:53 ` 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=20230619094637.4134449-1-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