All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: Joseph Zikusooka <josephzik@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] host-m4 build on Fedora 42 fails
Date: Mon, 21 Apr 2025 16:00:15 +0200	[thread overview]
Message-ID: <e07d34b22ea6c85e2d50249f1b06ccd9@free.fr> (raw)
In-Reply-To: <CAPWx8vtcjfVZJLydqyUAJ_8WbOHkrfJm2DG-qS5TO+msfa4uBQ@mail.gmail.com>

Hi Joseph,

On 19/04/2025 18:56, Joseph Zikusooka wrote:
> Hi Julien,
> 
> Thanks for the info and the workaround tip!
> 
> I updated my patch to use CFLAGS="$(HOST_CFLAGS) -std=gnu17" like you
> suggested, but the build still fails with GCC 15 and m4 1.4.19 - same
> errors as before. Strangely, if I build m4 outside the buildroot
> environment with those flags, it works fine.
> 
> Any idea what else could be causing the workaround to fail in
> buildroot? Are there other flags or tweaks I could try in m4.mk [1]
> until the new m4 release is out?

I just tried adding the line I suggested in package/m4/m4.mk:
HOST_M4_CONF_ENV = CFLAGS="$(HOST_CFLAGS) -std=gnu17"

On a Fedora 42 host system (updated as of now), it solves the
host-m4 build issue. You need to restart from a clean build,
though.

I tested with the commands:

     make qemu_aarch64_virt_defconfig
     make clean
     make

Could you check on your side, please?

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-04-21 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 14:14 [Buildroot] host-m4 build on Fedora 42 fails Joseph Zikusooka
2025-04-19 12:29 ` Julien Olivain
2025-04-19 16:56   ` Joseph Zikusooka
2025-04-21 14:00     ` Julien Olivain [this message]
2025-04-21 18:21       ` Joseph Zikusooka
2025-04-21 19:02         ` Joseph Zikusooka
2025-04-22 19:01           ` Julien Olivain

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=e07d34b22ea6c85e2d50249f1b06ccd9@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=josephzik@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.