From: Peter Korsgaard <peter@korsgaard.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org, Lothar Felten <lothar.felten@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/am33x-cm3: fix build with gcc >= 15
Date: Tue, 20 Oct 2026 12:18:37 +0200 [thread overview]
Message-ID: <87mrs8d69u.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20261014073743.3673307-1-dario.binacchi@amarulasolutions.com> (Dario Binacchi's message of "Wed, 14 Oct 2026 09:37:42 +0200")
>>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:
> gcc 15 defaults to the C23 standard, where bool, true and false are
> keywords. The am33x-cm3 code base defines them in its own stddef.h,
> so the build fails with:
> src/include/stddef.h:18:15: error: 'bool' cannot be defined via 'typedef'
> 18 | typedef _Bool bool;
> | ^~~~
> src/include/stddef.h:19:8: error: cannot use keyword 'false' as enumeration constant
> 19 | enum { false, true };
> | ^~~~~
> The upstream project has not received any commit since 2018 and none
> of its branches fix this issue, so rather than carrying a patch that
> cannot be submitted to an active upstream, force the GNU C11 standard
> in the .mk file.
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-20 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:37 [Buildroot] [PATCH 1/2] package/am33x-cm3: fix build with gcc >= 15 Dario Binacchi
2026-10-14 7:37 ` [Buildroot] [PATCH 2/2] configs/beaglebone: bump Linux to 6.18.56 and U-Boot to 2026.10 Dario Binacchi
2026-10-20 10:18 ` Peter Korsgaard
2026-10-20 10:18 ` Peter Korsgaard [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=87mrs8d69u.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=lothar.felten@gmail.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 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.