From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Aurelien DESBRIERES" <aurelien@hackers.camp>,
<openembedded-core@lists.openembedded.org>
Cc: <aurelien.desbrieres@gmail.com>
Subject: Re: [OE-core] [PATCH v2] flex: backport the upstream malloc prototype fix
Date: Tue, 15 Sep 2026 09:37:29 +0200 [thread overview]
Message-ID: <DLFPV7E70LU9.32YF2D5IUTKH8@bootlin.com> (raw)
In-Reply-To: <20260914085318.67139-1-aurelien@hackers.camp>
On Mon Sep 14, 2026 at 10:53 AM CEST, Aurelien DESBRIERES wrote:
> lib/malloc.c declares "void *malloc ();" with an empty parameter list
> and calls it with one argument. That meant "unspecified" in C89 and
> means "none" in C23, so a host compiler defaulting to C23 -- GCC 15 and
> later -- rejects the call:
>
> lib/malloc.c:16:15: error: too many arguments to function 'malloc';
> expected 0, have 1
>
> The file is built by stage1flex with the build host's compiler before
> flex can build itself, so neither CFLAGS nor BUILD_CFLAGS reaches that
> command line and no flag in the recipe can silence it.
>
> Upstream fixed it in bf254c75b1e0 and the patch falls out when flex
> next releases. Gentoo carries the same backport as
> flex-2.6.4-fix-malloc-prototype.patch.
This patch is already applied to flex on the master branch, from commit
e1832f02d70b ("flex: fix build with gcc-15 on host"). Maybe you need to rebase?
Antonin
next prev parent reply other threads:[~2026-09-15 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 16:05 [PATCH] flex: fix stage1flex build under a C23 default Aurelien DESBRIERES
2026-09-13 20:21 ` [OE-core] " Richard Purdie
2026-09-14 8:53 ` [PATCH v2] flex: backport the upstream malloc prototype fix Aurelien DESBRIERES
2026-09-15 7:37 ` Antonin Godard [this message]
2026-09-15 7:49 ` [OE-core] " Aurelien DESBRIERES
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=DLFPV7E70LU9.32YF2D5IUTKH8@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=aurelien.desbrieres@gmail.com \
--cc=aurelien@hackers.camp \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.