Re: [OE-core] [PATCH v2] python3: Add a new PACKAGECONFIG knob for free threading

["Böszörményi Zoltán" <zboszor@gmail.com>]

2026. 03. 23. 15:45 keltezéssel, Bartosz Golaszewski írta:
> On Mon, Mar 23, 2026 at 3:40 PM Böszörményi Zoltán <zboszor@gmail.com> wrote:
>> 2026. 03. 23. 15:34 keltezéssel, Bartosz Golaszewski írta:
>>> On Mon, 23 Mar 2026 15:23:52 +0100, "Zoltan Boszormenyi via
>>> lists.openembedded.org" <zboszor=gmail.com@lists.openembedded.org>
>>> said:
>>>>> Any hints on what could be wrong? The same config builds fine without the
>>>>> new option. It's just a core-image-minimal on poky with a few python packages
>>>>> from meta-openembedded.
>>>> The problem is that now the directories are
>>>> ${libdir}/python3.14t and ${includedir}/python3.14t
>>>>
>>>> Note the "t" suffix.
>>>>
>>>> diff --git a/meta/recipes-devtools/python/python3_3.14.3.bb
>>>> b/meta/recipes-devtools/python/python3_3.14.3.bb
>>>> index 7a1ad1e386..492f2f93f0 100644
>>>> --- a/meta/recipes-devtools/python/python3_3.14.3.bb
>>>> +++ b/meta/recipes-devtools/python/python3_3.14.3.bb
>>>> @@ -47,7 +47,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
>>>>
>>>>     CVE_PRODUCT = "python:python python_software_foundation:python cpython"
>>>>
>>>> -PYTHON_MAJMIN = "3.14"
>>>> +PYTHON_MAJMIN = "3.14${@bb.utils.contains('PACKAGECONFIG', 'freethreading', 't', '', d)}"
>>>>
>>>>     S = "${UNPACKDIR}/Python-${PV}"
>>>>
>>> I think it's more fine-grained, because I'm seeing this:
>> I also see other issues popping up, first in python3-installer-native.
>>
>> Probably this setting ("python-freethreading") should be a
>> DISTRO_FEATURE and then the python3 recipe would use that
>> to enable its PACKAGECONFIG.
>>
>> PYTHON_DIR in python-dir.bbclass should also be set accordingly.
>>
>> I suspect that both native and target builds of python3 would have
>> to use the same setting, i.e. DISTRO_FEATURE and DISTRO_FEATURE_NATIVE
>> must contain python-freethreading. Some build helpers (skbuild, etc.)
>> does not seem to distinguish correctly between host python and target.
>>
> But is there a config for which it ever worked?

Not really, this change was just a stab in the dark.
Probaly it should have been an RFC patch.