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: Tue, 22 Apr 2025 21:01:30 +0200	[thread overview]
Message-ID: <4388bcfc65382d2dd98db25748b6965a@free.fr> (raw)
In-Reply-To: <CAPWx8vvq0BgguhEfUnLt7-qm2kqTU4VCKjb7i2L+sXG9HbeOMQ@mail.gmail.com>

Hi Joseph,

On 21/04/2025 21:02, Joseph Zikusooka wrote:
> I think I rushed the previous patch - here’s the corrected version.
> 
> 
> --- a/package/m4/m4.mk    2025-04-03 13:59:27.224254338 +0300
> +++ b/package/m4/m4.mk     2025-04-21 21:41:45.589717302 +0300
> @@ -10,4 +10,6 @@
>  M4_LICENSE = GPL-3.0+
>  M4_LICENSE_FILES = COPYING
> 
> +HOST_M4_CONF_ENV = CFLAGS="$(HOST_CFLAGS) -std=gnu17"
> +
>  $(eval $(host-autotools-package))
> 
> On Mon, Apr 21, 2025 at 9:21 PM Joseph Zikusooka <josephzik@gmail.com> 
> wrote:
>> 
>> Hi Julien,
>> 
>> Thanks, that solved the problem! I needed to run "make distclean"
>> before building with the updated m4.mk file. While we wait for a new
>> m4 release from upstream, I’m sharing the patch that worked for me in
>> case anyone else encounters this issue.

Thank you for the confirmation. Could you send a new updated patch
with this fix, please?

Best regards,

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

      reply	other threads:[~2025-04-22 19:01 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
2025-04-21 18:21       ` Joseph Zikusooka
2025-04-21 19:02         ` Joseph Zikusooka
2025-04-22 19:01           ` Julien Olivain [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=4388bcfc65382d2dd98db25748b6965a@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.