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
Subject: Re: [Buildroot] [PATCH] package/flex: fix build with old host GCC since autoconf bump
Date: Wed, 26 Aug 2026 23:47:31 +0200	[thread overview]
Message-ID: <afc8ce49e89906c5e6b5947fe02119c1@free.fr> (raw)
In-Reply-To: <20260826154100.4144157-1-thomas.petazzoni@bootlin.com>

On 26/08/2026 17:41, Thomas Petazzoni via buildroot wrote:
> Since the bump of autoconf to version 2.73 in Buildroot commit, the
> build of target flex fails if the host compiler is too old, because
> the flex build system tries to use -std=gnu23 which isn't supported by
> older GCC releases, causing:
> 
> gcc: error: unrecognized command-line option '-std=gnu23'; did you mean 
> '-std=gnu2x'?
> gcc: error: unrecognized command-line option '-std=gnu23'; did you mean 
> '-std=gnu2x'?
> make[3]: *** [Makefile:1162: stage1flex-buf.o] Error 1
> 
> (Indeed the *target* flex package does build some host tools using the
> host GCC compiler.)
> 
> To fix this issue, we backport an upstream commit that isn't yet in
> any flex release.
> 
> Fixes:
> 
>   
> https://autobuild.buildroot.net/results/aac730b57adb5b54964f1054de781750952ef7d4/
> 
> 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-26 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 15:41 [Buildroot] [PATCH] package/flex: fix build with old host GCC since autoconf bump Thomas Petazzoni via buildroot
2026-08-26 21:47 ` Julien Olivain 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=afc8ce49e89906c5e6b5947fe02119c1@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --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