Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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-pecl-dbus: fix build with PHP8
Date: Wed, 6 Aug 2025 12:34:23 +0200	[thread overview]
Message-ID: <20250806123423.33451a9c@windsurf> (raw)
In-Reply-To: <DBV9S1S4XEEA.2DHT8AEV8PEL9@bootlin.com>

Hello Alexis,

On Wed, 06 Aug 2025 12:23:59 +0200
Alexis Lothoré <alexis.lothore@bootlin.com> wrote:

> Yes, I have those issues on the master branch, on 2fd520c8d52b
> ("package/glm: bump version to 1.0.1")

OK!

> > Is the issue
> > https://autobuild.buildroot.net/results/e98/e9892bbefa781b403fd3d834b6c48527c8e078ba/build-end.log
> > perhaps ? If so, please add a reference to the autobuilder failure.  
> 
> Yes, that looks like the same issue ! Ok, I'll add a reference.

Perfect.

> > For bug/build fixes, we like to understand since when the problem is
> > occurring, i.e which commit introduced the regression. If this package
> > was building on 2024.02 and no longer on 2025.02, I suspect it's one of
> > the PHP version bump between those two releases:  
> 
> The upstream commit in PHP project leading to this issue is actually the
> same as for the php-lua package (commit 91ef4124e56a ("Refactor
> zend_object_handlers API to pass zend_object* and zend_string* insted of
> zval(s)."), so the issue has been introduced when the PHP packaged has been
> bumped to 8.0.0, not later. And again, I can see the issue with a minimal
> defconfig _when using bootlin bleeding-edge toolchain_. With stable
> toolchain, we can spot the corresponding warning in php-dbus build logs,
> but it is not turned into an actual error.

Ah, OK. I was wondering then why the issue was not happening with
Buildroot 2024.02 which already had PHP >= 8.0.0.

So it's really the switch to GCC 15.x that exhibits the issue, turning
it into a hard build error.

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

  reply	other threads:[~2025-08-06 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  8:53 [Buildroot] [PATCH] package/php-pecl-dbus: fix build with PHP8 Alexis Lothoré via buildroot
2025-08-06  9:08 ` Thomas Petazzoni via buildroot
2025-08-06 10:23   ` Alexis Lothoré via buildroot
2025-08-06 10:34     ` Thomas Petazzoni via buildroot [this message]
2025-08-06 12:14       ` Alexis Lothoré via buildroot
2025-08-06 14:52         ` 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=20250806123423.33451a9c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox