Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Romain Naour" <romain.naour@smile.fr>, <buildroot@buildroot.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Hervé Codina" <herve.codina@bootlin.com>,
	"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>
Subject: Re: [Buildroot] [PATCH v3] package/php-lua: fix build with PHP8/GCC14
Date: Mon, 08 Sep 2025 08:40:28 +0200	[thread overview]
Message-ID: <DCN7OW3PFUKS.1KAEWCJEF19V7@bootlin.com> (raw)
In-Reply-To: <8c92dae4-f2f8-47c6-ba3c-79414815bc31@smile.fr>

Hi Romain,

On Sun Sep 7, 2025 at 12:17 AM CEST, Romain Naour wrote:
> Hello Alexis, All,
>
> Le 25/08/2025 à 16:53, Alexis Lothoré a écrit :
>> Hi Romain,
>> 
>> On Sun Aug 24, 2025 at 5:36 PM CEST, Romain Naour wrote:
>>> Hello Alexis, Thomas, All,
>>>
>>> Le 11/08/2025 à 09:52, Alexis Lothoré via buildroot a écrit :

[...]

>> My bad for the absence of reaction on my side, I have been off for a few
>> days, and then travelling for conference. Thanks for handling this !
>
> No problem, thanks for your contribution in the first place.
>
> I noticed a new issue in Gitlab-CI that seems related to this patch [1]
> Indeed, the backported commit [2] introduce a build issue with lua < 502
> interpreters due to probably a copy past of this line (val is not defined):
>
>   lua_pushlstring(L, ZSTR_VAL(val), ZSTR_LEN(val));
>
> I guess, we have to replace "val" by "member" since ZSTR_VAL macro uses internal
> "(zstr)->val" (#define ZSTR_VAL(zstr)  (zstr)->val) that seems only available in
> "member". But I may be wrong...
>
>   lua_pushlstring(L, ZSTR_VAL(member), ZSTR_LEN(member));
>
> With that fixed, TestPhpLuaLuajit pass.
>
> Can you have a look?
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/11176774941
> [2] https://github.com/badoo/php-lua/commit/de1068d634519abf2461dac9427b5ff24b6603af

Sure, I'll look at it and submit the relevant patch.

Alexis
>
> Best regards,
> Romain
>
>
>> 
>> Alexis
>> 
>>> Best regards,
>>> Romain
>>>
>> 




-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

  reply	other threads:[~2025-09-08  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11  7:52 [Buildroot] [PATCH v3] package/php-lua: fix build with PHP8/GCC14 Alexis Lothoré via buildroot
2025-08-24 15:36 ` Romain Naour via buildroot
2025-08-25 14:53   ` Alexis Lothoré via buildroot
2025-09-06 22:17     ` Romain Naour via buildroot
2025-09-08  6:40       ` Alexis Lothoré via buildroot [this message]
2025-09-08 10:55 ` Thomas Perale via buildroot
2025-09-08 11:20   ` Baruch Siach via buildroot
2025-09-08 13:13     ` Thomas Perale via buildroot
2025-09-08 13:32       ` Baruch Siach via buildroot
2025-09-10  8:36       ` Romain Naour via buildroot
2025-09-19 12:56 ` Thomas Perale 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=DCN7OW3PFUKS.1KAEWCJEF19V7@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=herve.codina@bootlin.com \
    --cc=nicolas.carrier@nav-timing.safrangroup.com \
    --cc=romain.naour@smile.fr \
    --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