From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [Buildroot] [PATCH 1/1] package/fio: fix build
Date: Fri, 2 Jan 2026 21:52:28 +0100 [thread overview]
Message-ID: <20260102215228.26b88159@windsurf> (raw)
In-Reply-To: <20260102201743.3421271-1-bernd@kuhls.net>
On Fri, 2 Jan 2026 21:17:43 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Buildroot commit 215133c0fc2819f059fbb35071ab2e0987f5107d bumped fio from
> 3.38 to 3.41. Upstream commit
> https://github.com/axboe/fio/commit/4175f4dbec5d1d9e5e0490026e98b1806188e098
> was added to fio 3.40 including FALLOC_FL_ZERO_RANGE which causes build
> errors.
>
> Added upstream commit which not only fixes musl builds but also uclibc.
>
> Fixes:
> musl: https://autobuild.buildroot.net/results/8e9/8e946c7104be0295a9a2b946fe4a82bba0e28db8/
> uclibc: https://autobuild.buildroot.net/results/ece/ece6ff1b20fa3482a88ffb3a6167b2bba9b06101/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/fio/0001-fix-musl-builds.patch | 38 ++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 package/fio/0001-fix-musl-builds.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-02 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 20:17 [Buildroot] [PATCH 1/1] package/fio: fix build Bernd Kuhls
2026-01-02 20:52 ` Thomas Petazzoni via buildroot [this message]
2026-01-13 19:48 ` Arnout Vandecappelle via buildroot
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=20260102215228.26b88159@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=thomas.petazzoni@bootlin.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