From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Jules Maselbas <jmaselbas@zdiv.net>
Subject: Re: [PATCH master 0/3] sandbox: enable building under musl
Date: Thu, 27 Mar 2025 09:13:51 +0100 [thread overview]
Message-ID: <174306323109.810869.3518539069422342683.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250325124740.4035964-1-a.fatoum@pengutronix.de>
On Tue, 25 Mar 2025 13:47:37 +0100, Ahmad Fatoum wrote:
> Building sandbox itself as opposed to the target/host tools still fails
> with musl, due to some headers not being available.
>
> This is fixed by this series.
>
> Ahmad Fatoum (3):
> sandbox: use POSIX header instead of Linux one
> sandbox: don't build tap support code without CONFIG_DRIVER_NET_TAP
> sandbox: os: tap: make it compile with musl
>
> [...]
Applied, thanks!
[1/3] sandbox: use POSIX header instead of Linux one
https://git.pengutronix.de/cgit/barebox/commit/?id=1426b121630e (link may not be stable)
[2/3] sandbox: don't build tap support code without CONFIG_DRIVER_NET_TAP
https://git.pengutronix.de/cgit/barebox/commit/?id=97fcb63d9d67 (link may not be stable)
[3/3] sandbox: os: tap: make it compile with musl
https://git.pengutronix.de/cgit/barebox/commit/?id=d9e696e5a5dd (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-03-27 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 12:47 Ahmad Fatoum
2025-03-25 12:47 ` [PATCH master 1/3] sandbox: use POSIX header instead of Linux one Ahmad Fatoum
2025-03-25 12:47 ` [PATCH master 2/3] sandbox: don't build tap support code without CONFIG_DRIVER_NET_TAP Ahmad Fatoum
2025-03-25 12:47 ` [PATCH master 3/3] sandbox: os: tap: make it compile with musl Ahmad Fatoum
2025-03-27 8:13 ` Sascha Hauer [this message]
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=174306323109.810869.3518539069422342683.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@zdiv.net \
/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