Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
	Joseph Kogut <joseph.kogut@gmail.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/mesa3d: fix build issue with gcc < 13
Date: Thu, 27 Aug 2026 22:43:44 +0200	[thread overview]
Message-ID: <dcdd783ea4c1670ae760b0e08b235ce3@free.fr> (raw)
In-Reply-To: <20260826141337.4035888-1-thomas.petazzoni@bootlin.com>

On 26/08/2026 16:13, Thomas Petazzoni via buildroot wrote:
> Since upstream commit
> e42e3193137d1b21e84b499336e7a8887b8a8689 ("intel: add Jay"), a C23
> construct is used in the intel driver code:
> 
> enum jay_predication : uint8_t
> 
> This causes a build issue with GCC < 13:
> 
> In file included from ../src/intel/compiler/jay/jay_builder.h:12,
>                  from ../src/intel/compiler/jay/jay_from_nir.c:23:
> ../src/intel/compiler/jay/jay_ir.h:582:22: error: expected identifier 
> or ‘(’ before ‘:’ token
>   582 | enum jay_predication : uint8_t {
>       |                      ^
> ../src/intel/compiler/jay/jay_ir.h:637:25: error: field ‘predication’ 
> has incomplete type
>   637 |    enum jay_predication predication;
>       |                         ^~~~~~~~~~~
> 
> We fix that by integrating a patch already available in
> OpenEmbedded. It changes the code to not use the C23 construct.
> 
> This build issue was encountered on host-mesa3d while building an
> allyespackageconfig configuration inside our standard Docker
> container.
> 
> Buildroot commit
> c073c976179021c84e0c84f6f23e938b43783e75 ("package/{mesa3d,
> mesa3d-headers}: bump version to 26.1.0") that switched to mesa3d
> 26.1.0, which contains the problematic commit. Therefore 2026.05 is
> affected, but not earlier Buildroot versions.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-27 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 14:13 [Buildroot] [PATCH] package/mesa3d: fix build issue with gcc < 13 Thomas Petazzoni via buildroot
2026-08-27 20:43 ` Julien Olivain via buildroot [this message]
2026-09-04 12:17 ` Thomas Perale 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=dcdd783ea4c1670ae760b0e08b235ce3@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=joseph.kogut@gmail.com \
    --cc=ju.o@free.fr \
    --cc=romain.naour@gmail.com \
    --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