From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org, Gilles Talis <gilles.talis@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/iozone: fix parallel build of the linux-noaio target
Date: Fri, 23 Oct 2026 09:31:41 +0200 [thread overview]
Message-ID: <atsNNhuRk7k0lFDr@windsurf> (raw)
In-Reply-To: <20261022222752.3530250-1-yegorslists@googlemail.com>
On Fri, Oct 23, 2026 at 12:27:51AM +0200, Yegor Yefremov wrote:
> With uClibc, iozone is built with the linux-noaio target, which lists
> libbif.o as a prerequisite although libbif.o is built by the
> iozone_linux-noaio.o rule. With a parallel build, make also builds
> libbif.o with its built-in rule, without -DHAVE_ANSIC_C, so the K&R
> code path is used, which fails with GCC >= 15 (C23):
>
> libbif.c:191:1: error: number of arguments doesn't match prototype
> libbif.c:170:1: error: prototype declaration
> libbif.c:193:9: error: too many arguments to function 'do_eof'; expected 0, have 1
>
> Commit d7233ae04854 ("package/iozone: Fix parallel build problem")
> fixed the same issue for the linux targets only. Add a patch doing the
> same for the linux-noaio and linux-noth targets, which were added by
> 0001-Add-new-targets-for-iozone.patch.
>
> This issue has been present since commit 75891397abe6 ("package/gcc:
> add support for GCC 15.x"); before GCC 15, libbif.c built with the
> wrong flags but didn't fail. It therefore affects 2025.08 and later,
> i.e. 2025.11.x, 2026.02.x, 2026.05.x and 2026.08.x when GCC 15 is used.
>
> Fixes: 75891397abe60dbe3d82a1ec39654ff81d1b1406 ("package/gcc: add support for GCC 15.x")
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
I initially had a hard time to understand how a parallel build issue
could be related to a GCC version, but your commit log explained it
very well, thanks for that.
Both patches applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-23 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 22:27 [Buildroot] [PATCH 1/2] package/iozone: fix parallel build of the linux-noaio target Yegor Yefremov
2026-10-22 22:27 ` [Buildroot] [PATCH 2/2] package/iozone: bump to version 3.511 Yegor Yefremov
2026-10-23 7:31 ` Thomas Petazzoni via buildroot [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=atsNNhuRk7k0lFDr@windsurf \
--to=buildroot@buildroot.org \
--cc=gilles.talis@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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