From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org,
"Hervé Codina" <herve.codina@bootlin.com>,
"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>
Subject: Re: [Buildroot] [PATCH] package/php-lua: fix build with GCC14
Date: Wed, 6 Aug 2025 12:35:37 +0200 [thread overview]
Message-ID: <20250806123537.16a594a3@windsurf> (raw)
In-Reply-To: <DBV97YP0K6IX.5WJ4MF4JBM8H@bootlin.com>
Hello Alexis,
On Wed, 06 Aug 2025 11:57:45 +0200
Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
> > Also, do you know what caused the failure? I would suspect an update of
> > PHP.
>
> If I trust the upstream pending PR, the failure is due to commit
> 91ef4124e56a ("Refactor zend_object_handlers API to pass zend_object* and
> zend_string* insted of zval(s).") in upstream PHP project. I fail to find
> the corresponding entry in any PHP changelog, but following the git
> history, this has been introduced with PHP 8.0.0. I tried to quickly revert
> to PHP 7.4.20, but this version does not even build anymore on
> current BR (unrelated build failures)
>
> However I observe that if I switch from Bootlin 'bleeding edge' toolchain
> to 'stable' toolchain, php-lua build succeeds on master. So I guess this
> issue is a mix of API change and compiler update. When using the stable
> toolchain, I see the warning that matches the error I see when using the
> bleeding-edge toolchain (-Wincompatible-pointer-types)
As pointed out in my other e-mail replying to your other patch, this
definitely sounds like a GCC 15.x related issue, where GCC 15.x enabled
more checks, causing a hard build failure where "simple" warnings were
emitted earlier.
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
prev parent reply other threads:[~2025-08-06 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:12 [Buildroot] [PATCH] package/php-lua: fix build with GCC14 Alexis Lothoré via buildroot
2025-08-06 8:57 ` Thomas Petazzoni via buildroot
2025-08-06 9:57 ` Alexis Lothoré via buildroot
2025-08-06 10:35 ` Thomas Petazzoni 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=20250806123537.16a594a3@windsurf \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=herve.codina@bootlin.com \
--cc=nicolas.carrier@nav-timing.safrangroup.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.