From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@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, 06 Aug 2025 11:57:45 +0200 [thread overview]
Message-ID: <DBV97YP0K6IX.5WJ4MF4JBM8H@bootlin.com> (raw)
In-Reply-To: <20250806105707.3db4f1e8@windsurf>
Hi Thomas,
On Wed Aug 6, 2025 at 10:57 AM CEST, Thomas Petazzoni wrote:
> Hello Alexis,
>
> On Wed, 06 Aug 2025 10:12:49 +0200
> Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
>
>> On Buildroot 2025.02.x, php-lua build fails on the following error:
>
> Buildroot 2025.02.x is one thing, but do you also see the same build
> issue on master?
Yes, I have the build failure on top of master as well (on top of
2fd520c8d52b ("package/glm: bump version to 1.0.1"), to be precise)
>
> Since there's no build failure in our autobuilder (which is kind of
> surprising), could you include in the commit log a snippet of a
> reasonably minimal defconfig that exhibits the issue?
Sure, I'll include it in the next revision. It looks like this:
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_ARM_FPU_NEON=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_PACKAGE_LUA=y
BR2_PACKAGE_PHP=y
BR2_PACKAGE_PHP_LUA=y
BR2_PACKAGE_PHP_PECL_DBUS=y
> 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)
>> I've taken a look at the official upstream to make the fix integrated in
>> here as well, but it really looks like a dead end: there has been no
>> activity for 5 years, and the maintainer does not seem to answer PRs or
>> issues. The PR containing the two patches introduced with the BR package
>> has not even been merged. I have been tempted to replace the upstream
>> source with the fork from which I took the patch
>> (https://github.com/badoo/php-lua), which looks slightly less "dead"
>> (last activity 2 years ago, and some work done to update the module
>> compatibility with current PHP major version). I eventually chose to
>> keep the current upstream and bring this single patch, but please let me
>> know if changing the upstream source would be better.
>
> It's of course annoying to have unmaintained things packaged in
> Buildroot. I guess Nicolas is still using this software component?
>
> Thomas
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-06 9:57 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 [this message]
2025-08-06 10:35 ` Thomas Petazzoni via buildroot
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=DBV97YP0K6IX.5WJ4MF4JBM8H@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox