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] package/iozone: fix build without ASYNC_IO with GCC >= 15
Date: Thu, 22 Oct 2026 23:23:54 +0200 [thread overview]
Message-ID: <atp-5quxInY8VV1h@windsurf> (raw)
In-Reply-To: <20261022205926.3431624-1-yegorslists@googlemail.com>
On Thu, Oct 22, 2026 at 10:59:26PM +0200, Yegor Yefremov wrote:
> With uClibc, iozone is built with the linux-noaio target, where the
> async_*() stubs are declared and defined without parameter lists. GCC 15
> defaults to C23, where an empty parameter list means the function takes
> no arguments, so the build fails:
>
> iozone.c:8150:32: error: too many arguments to function 'async_write_no_copy'; expected 0, have 7
> iozone.c:9126:31: error: too many arguments to function 'async_read_no_copy'; expected 0, have 8
> iozone.c:20165:1: error: conflicting types for 'async_init'; have 'void(void)'
>
> Add a patch, sent upstream, that gives the stubs full prototypes
> matching their ASYNC_IO counterparts. iozone 3.510, the latest release,
> still has the same stubs, so a version bump wouldn't help.
>
> This issue has been present since commit 75891397abe6 ("package/gcc:
> add support for GCC 15.x"), as GCC 15 is the first version defaulting
> to C23. 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. 2025.02.x is
> not affected as it doesn't support GCC 15.
>
> Fixes:
> https://autobuild.buildroot.org/results/4090fb0d0a3b8bee60707b1672c35dada744bff5
>
> 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>
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-22 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 20:59 [Buildroot] [PATCH] package/iozone: fix build without ASYNC_IO with GCC >= 15 Yegor Yefremov
2026-10-22 21:23 ` 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=atp-5quxInY8VV1h@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