From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/2] ci: add new musl-tools Github CI workflow
Date: Thu, 5 Jun 2025 13:25:24 +0200 [thread overview]
Message-ID: <20250605112524.1958636-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250605112524.1958636-1-a.fatoum@pengutronix.de>
To avoid noticing musl breakage when barebox is updated in
OpenEmbedded-core, let's add a CI test at our side as well.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.github/workflows/musl-tools.yml | 39 ++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 .github/workflows/musl-tools.yml
diff --git a/.github/workflows/musl-tools.yml b/.github/workflows/musl-tools.yml
new file mode 100644
index 000000000000..52cdd184ade3
--- /dev/null
+++ b/.github/workflows/musl-tools.yml
@@ -0,0 +1,39 @@
+name: build tools against musl
+
+on: [push, pull_request]
+
+jobs:
+ musl-tools:
+ runs-on: ubuntu-latest
+ container:
+ image: ghcr.io/barebox/barebox/barebox-ci:latest
+ # allow mounting and devtmpfs in the container
+ options: --user=root --privileged -v /dev:/dev
+
+ strategy:
+ fail-fast: false
+ matrix:
+
+ include:
+ - defconfig: hosttools_defconfig
+ suffix:
+
+ - defconfig: targettools_defconfig
+ suffix: -target
+
+ steps:
+ - name: Checkout code
+ uses: actions/checkout@v4
+
+ - name: Build
+ id: build
+ run: |
+ export PKG_CONFIG='pkg-config --keep-system-libs'
+ export CROSS_PKG_CONFIG='pkg-config --keep-system-libs'
+
+ m () { make -j$(nproc) CC=musl-gcc LD=musl-gcc HOSTCC=musl-gcc HOSTLD=musl-ld "$@"; }
+
+ m ${{matrix.defconfig}}
+ m scripts/
+
+ test -n "$(musl-ldd scripts/imx/imx-usb-loader${{matrix.suffix}} 2>/dev/null | grep musl)"
--
2.39.5
next prev parent reply other threads:[~2025-06-05 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:25 [PATCH 1/2] scripts: rockchip: rename SECTOR_SIZE/PAGE_SIZE Ahmad Fatoum
2025-06-05 11:25 ` Ahmad Fatoum [this message]
2025-06-05 11:54 ` 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=20250605112524.1958636-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