From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "François PERRAD" <francois.perrad.86@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 3/3] package/lua-lunix: fix incompatible pointer types
Date: Sun, 13 Sep 2026 11:43:00 +0200 [thread overview]
Message-ID: <aqZvcahE2rYBiBL6@windsurf> (raw)
In-Reply-To: <CAMTop881hu=pLy=3N+rPNtorZFawAC54-xfvWbfAaPz7UrE+Bg@mail.gmail.com>
On Sun, Sep 13, 2026 at 11:30:45AM +0200, François PERRAD wrote:
> the version (= date) of this package is quite old : 20220331
> on autobuild, there are failures, only since 2026 (see [4]https://
> autobuild.buildroot.org/?reason=lua-lunix-20220331-1&step=100)
> so, I think that the issue is appeared with gcc 15.
Thanks, but we need more than "I think". Test the build with gcc 14,
then gcc 15, and verify if that is really the thing that causes the
build failure. Otherwise it's basically us maintainers who have to do
this, and we have 700+ pending patches that need review, which is why
we are asking contributors to do this investigation effort.
Thanks for your contribution!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-13 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:06 [Buildroot] [PATCH 1/3] package/luasyslog: bump to version 2.2.2 Francois Perrad
2026-09-11 8:06 ` [Buildroot] [PATCH 2/3] package/luv: bump to version 1.52.1-0 Francois Perrad
2026-09-11 8:06 ` [Buildroot] [PATCH 3/3] package/lua-lunix: fix incompatible pointer types Francois Perrad
2026-09-13 7:35 ` Thomas Petazzoni via buildroot
2026-09-13 9:30 ` François PERRAD
2026-09-13 9:43 ` Thomas Petazzoni via buildroot [this message]
2026-09-13 19:03 ` François PERRAD
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=aqZvcahE2rYBiBL6@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad.86@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 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.