Skip to contentSkip to conversation

python3: Add a new PACKAGECONFIG knob for free threading

PATCH In review Zoltán Böszörményi 4 participants 18 messages Mar 12 – Mar 25 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 python3: Add a new PACKAGECONFIG knob for free threading

One of the main points in the Python 3.14.x release notes was that free threading is officially supported.

Add PACKAGECONFIG[freethreading] to turn it on with --disable-gil. GIL is the Global Interpreter Lock, which is kept enabled without this option.

By default, keep free threading disabled, i.e. GIL enabled.

---
 meta/recipes-devtools/python/python3_3.14.3.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-devtools/python/python3_3.14.3.bb +1 -0
index 7047cd8e8d..7a1ad1e386 100644
@@ -112,6 +112,7 @@ CACHED_CONFIGUREVARS:append:libc-musl = "\
 
 # PGO currently causes builds to not be reproducible so disable by default, see YOCTO #13407
 PACKAGECONFIG ??= "editline gdbm ${@bb.utils.filter('DISTRO_FEATURES', 'lto', d)}"
+PACKAGECONFIG[freethreading] = "--disable-gil,--enable-gil"
 PACKAGECONFIG[readline] = "--with-readline=readline,,readline,,,editline"
 PACKAGECONFIG[editline] = "--with-readline=editline,,libedit,,,readline"
 # Use profile guided optimisation by running PyBench inside qemu-user
Signature · 1 line
2.53.0
#1 lore raw
Quoted 27 lines · Zoltan Boszormenyi via lists.openembedded.org

One of the main points in the Python 3.14.x release notes was that free threading is officially supported.

Add PACKAGECONFIG[freethreading] to turn it on with --disable-gil. GIL is the Global Interpreter Lock, which is kept enabled without this option.

By default, keep free threading disabled, i.e. GIL enabled.

---
 meta/recipes-devtools/python/python3_3.14.3.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
index 7047cd8e8d..7a1ad1e386 100644
@@ -112,6 +112,7 @@ CACHED_CONFIGUREVARS:append:libc-musl = "\
 
 # PGO currently causes builds to not be reproducible so disable by default, see YOCTO #13407
 PACKAGECONFIG ??= "editline gdbm ${@bb.utils.filter('DISTRO_FEATURES', 'lto', d)}"
+PACKAGECONFIG[freethreading] = "--disable-gil,--enable-gil"
 PACKAGECONFIG[readline] = "--with-readline=readline,,readline,,,editline"
 PACKAGECONFIG[editline] = "--with-readline=editline,,libedit,,,readline"
 # Use profile guided optimisation by running PyBench inside qemu-user
--
Quoted 2 lines

2.53.0

Thanks for doing this, I'm really interested in using free-threaded python on Yocto. However, when trying to enable this with current openembedded-core, I ran into the following problem:

Loading cache: 100% |###############################################################################################################################################################################################################################################################|
Time: 0:00:02
Loaded 5224 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION           = "2.16.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
SDKMACHINE           = "x86_64"
DISTRO               = "poky"
DISTRO_VERSION       =
"5.3.99+snapshot-8061433fcd11eba91a29004dfafd175d449fb2fd"
TUNE_FEATURES        = "m64 x86-64-v3"
meta                 = "master:8061433fcd11eba91a29004dfafd175d449fb2fd"
meta-poky            = "master:c7fa63bea78248597798739aa4da49a9f4405b9c"

meta-oe
meta-python
meta-networking
meta-filesystems = "master:b883bd25cdd27560fdebc5a4bf56f90e99964c4c"

Sstate summary: Wanted 254 Local 2 Mirrors 0 Missed 252 Current 2392
(0% match, 90% complete)#############################################################################################################################################################

                         | ETA:  0:00:00

Initialising tasks: 100% |##########################################################################################################################################################################################################################################################|
Time: 0:00:05
NOTE: Executing Tasks
ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to
find header python3.14/pyconfig.h.
ERROR: python3-3.14.3-r0 do_install: Execution of
'/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/run.do_install.2092850'
failed with exit code 1
ERROR: Logfile of failure stored in:
/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_install.2092850
ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 4513 tasks of which 4512 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_install

    log: /home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_install.2092850

Summary: There were 2 ERROR messages, returning a non-zero exit code.

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.

Thanks in advance,
Bartosz

#2 lore raw
Quoted 5 lines · Bartosz Golaszewski

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.
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.

This is the error? ^^^

Alex

#3 lore raw
Quoted 11 lines · Alexander Kanavin
Quoted 5 lines · Bartosz Golaszewski

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.
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.

This is the error? ^^^

As in: pulling in packages from meta-openembedded? Not sure what you mean, this shouldn't have any impact as the offending recipe is python itself.

But ok, I disabled meta-openembedded and it fails the same with the only additional package being python3.

Bart

#4 lore raw
Quoted 2 lines · Bartosz Golaszewski
Quoted 2 lines
Quoted 2 lines

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.

^^^ This.

Quoted 7 lines
Quoted 6 lines
Quoted 3 lines

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.

This is the error? ^^^

Quoted 6 lines

As in: pulling in packages from meta-openembedded? Not sure what you mean, this shouldn't have any impact as the offending recipe is python itself.

But ok, I disabled meta-openembedded and it fails the same with the only additional package being python3.

No. This error:

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.

Alex

Alex

#5 lore raw
Quoted 18 lines · Alexander Kanavin
Quoted 2 lines · Bartosz Golaszewski
Quoted 2 lines
Quoted 2 lines

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.

^^^ This.

Quoted 11 lines
Quoted 6 lines
Quoted 3 lines

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.

This is the error? ^^^

As in: pulling in packages from meta-openembedded? Not sure what you mean, this shouldn't have any impact as the offending recipe is python itself.

Quoted 8 lines
Quoted 2 lines

But ok, I disabled meta-openembedded and it fails the same with the only additional package being python3.

No. This error:

ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to find header python3.14/pyconfig.h.

Yes, that seems to be the error though the file is there under recipe-sysroot-native.

Bart

#6 lore raw
In reply to Bartosz Golaszewski

2026. 03. 23. 14:28 keltezéssel, Bartosz Golaszewski írta:

Quoted 80 lines
Quoted 27 lines · Zoltan Boszormenyi via lists.openembedded.org

One of the main points in the Python 3.14.x release notes was that free threading is officially supported.

Add PACKAGECONFIG[freethreading] to turn it on with --disable-gil. GIL is the Global Interpreter Lock, which is kept enabled without this option.

By default, keep free threading disabled, i.e. GIL enabled.

---
  meta/recipes-devtools/python/python3_3.14.3.bb | 1 +
  1 file changed, 1 insertion(+)
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
index 7047cd8e8d..7a1ad1e386 100644
@@ -112,6 +112,7 @@ CACHED_CONFIGUREVARS:append:libc-musl = "\
 
  # PGO currently causes builds to not be reproducible so disable by default, see YOCTO #13407
  PACKAGECONFIG ??= "editline gdbm ${@bb.utils.filter('DISTRO_FEATURES', 'lto', d)}"
+PACKAGECONFIG[freethreading] = "--disable-gil,--enable-gil"
  PACKAGECONFIG[readline] = "--with-readline=readline,,readline,,,editline"
  PACKAGECONFIG[editline] = "--with-readline=editline,,libedit,,,readline"
  # Use profile guided optimisation by running PyBench inside qemu-user
--
Quoted 2 lines

2.53.0

Thanks for doing this, I'm really interested in using free-threaded python on Yocto. However, when trying to enable this with current openembedded-core, I ran into the following problem:

Loading cache: 100% |###############################################################################################################################################################################################################################################################|
Time: 0:00:02
Loaded 5224 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION           = "2.16.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
SDKMACHINE           = "x86_64"
DISTRO               = "poky"
DISTRO_VERSION       =
"5.3.99+snapshot-8061433fcd11eba91a29004dfafd175d449fb2fd"
TUNE_FEATURES        = "m64 x86-64-v3"
meta                 = "master:8061433fcd11eba91a29004dfafd175d449fb2fd"
meta-poky            = "master:c7fa63bea78248597798739aa4da49a9f4405b9c"

meta-oe
meta-python
meta-networking
meta-filesystems = "master:b883bd25cdd27560fdebc5a4bf56f90e99964c4c"

Sstate summary: Wanted 254 Local 2 Mirrors 0 Missed 252 Current 2392
(0% match, 90% complete)#############################################################################################################################################################

                          | ETA:  0:00:00

Initialising tasks: 100% |##########################################################################################################################################################################################################################################################|
Time: 0:00:05
NOTE: Executing Tasks
ERROR: python3-3.14.3-r0 do_install: oe_multilib_header: Unable to
find header python3.14/pyconfig.h.
ERROR: python3-3.14.3-r0 do_install: Execution of
'/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/run.do_install.2092850'
failed with exit code 1
ERROR: Logfile of failure stored in:
/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_install.2092850
ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 4513 tasks of which 4512 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:

Quoted 8 lines
   /home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_install
     log: /home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_install.2092850

Summary: There were 2 ERROR messages, returning a non-zero exit code.

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644
@@ -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}"

#7 lore raw
Quoted 16 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 4 lines

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644

meta/recipes-devtools/python/python3_3.14.3.bb UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar" · line 53

Quoted 8 lines
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
@@ -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:

ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3-iniconfig_2.3.0.bb:do_prepare_recipe_sysroot) failed with exit code '1'
ERROR: python3-3.14.3-r0 do_package: QA Issue: python3:
Files/directories were installed but not shipped in any package:
/usr/bin/python3.14
Please set FILES such that these items are packaged. Alternatively if
they are unneeded, avoid installing them or delete them within
do_install.
python3: 1 installed and not shipped files. [installed-vs-shipped]
ERROR: python3-3.14.3-r0 do_package: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in:
/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_package.2308607
ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_package) failed with exit code '1'

The MAJMIN seems to be used for the executable as well and with this change, it's missing from FILES.

Bart

#8 lore raw

2026. 03. 23. 15:34 keltezéssel, Bartosz Golaszewski írta:

Quoted 18 lines
Quoted 15 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 3 lines

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644
@@ -47,7 +47,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
 
Quoted 8 lines

meta/recipes-devtools/python/python3_3.14.3.bb UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar" · line 53

Quoted 7 lines
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
   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.

Quoted 19 lines

ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3-iniconfig_2.3.0.bb:do_prepare_recipe_sysroot) failed with exit code '1'
ERROR: python3-3.14.3-r0 do_package: QA Issue: python3:
Files/directories were installed but not shipped in any package:

   /usr/bin/python3.14

Please set FILES such that these items are packaged. Alternatively if
they are unneeded, avoid installing them or delete them within
do_install.
python3: 1 installed and not shipped files. [installed-vs-shipped]
ERROR: python3-3.14.3-r0 do_package: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in:
/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_package.2308607
ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_package) failed with exit code '1'

The MAJMIN seems to be used for the executable as well and with this change, it's missing from FILES.

Bart

#9 lore raw
Quoted 7 lines · Böszörményi Zoltán

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.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Alex

#10 lore raw

2026. 03. 23. 15:47 keltezéssel, Alexander Kanavin írta:

Quoted 10 lines · Böszörményi Zoltán
Quoted 7 lines

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.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Which implies doubling every python3-* recipes, too.

#11 lore raw
Quoted 8 lines · Zoltan Boszormenyi via lists.openembedded.org

2026. 03. 23. 15:47 keltezéssel, Alexander Kanavin írta:

Quoted 7 lines · Böszörményi Zoltán
Quoted 6 lines

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.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

PYTHON_DIR in python-dir.bbclass should also be set accordingly.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Which implies doubling every python3-* recipes, too.

I think that should only be for python3 packages which actually have binary builds.

For example, python3-setuptools should still be fine, but python3-pyyaml would also need threading enabled for the recipe.

Unfortunately that means this gets even more complicated.

We may need to come up with a couple of new variables and/or a class for threaded builds to make the threaded versions work.

Quoted 10 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#233742): https://lists.openembedded.org/g/openembedded-core/message/233742
Mute This Topic: https://lists.openembedded.org/mt/118277380/7611679
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#12 lore raw

2026. 03. 23. 16:03 keltezéssel, Trevor Gamblin írta:

Quoted 10 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 8 lines

2026. 03. 23. 15:47 keltezéssel, Alexander Kanavin írta:

Quoted 7 lines · Böszörményi Zoltán
Quoted 6 lines

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.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

PYTHON_DIR in python-dir.bbclass should also be set accordingly.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Which implies doubling every python3-* recipes, too.

I think that should only be for python3 packages which actually have binary builds.

Not just those. Script-only modules won't be found either by one build in the the other build's site-packages.

Quoted 16 lines

For example, python3-setuptools should still be fine, but python3-pyyaml would also need threading enabled for the recipe.

Unfortunately that means this gets even more complicated.

We may need to come up with a couple of new variables and/or a class for threaded builds to make the threaded versions work.

Quoted 10 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#233742): https://lists.openembedded.org/g/openembedded-core/message/233742
Mute This Topic: https://lists.openembedded.org/mt/118277380/7611679
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#13 lore raw
Quoted 16 lines · Böszörményi Zoltán

2026. 03. 23. 16:03 keltezéssel, Trevor Gamblin írta:

Quoted 14 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 12 lines

2026. 03. 23. 15:47 keltezéssel, Alexander Kanavin írta:

Quoted 10 lines · Böszörményi Zoltán
Quoted 7 lines

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.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Which implies doubling every python3-* recipes, too.

I think that should only be for python3 packages which actually have binary builds.

Not just those. Script-only modules won't be found either by one build in the the other build's site-packages.

Am I getting this right: This is experimental, never worked and actually shouldn't even be in openembedded-core master at all? I'm trying to figure out if I'm wasting my time trying to make this work.

Bart

#14 lore raw

2026. 03. 24. 9:46 keltezéssel, Bartosz Golaszewski írta:

Quoted 14 lines · Böszörményi Zoltán
Quoted 13 lines

2026. 03. 23. 16:03 keltezéssel, Trevor Gamblin írta:

Quoted 12 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 11 lines

2026. 03. 23. 15:47 keltezéssel, Alexander Kanavin írta:

Quoted 10 lines · Böszörményi Zoltán
Quoted 7 lines

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.

In patch review it was suggested that we should actually have two co-installable recipes, rather than an exclusive choice between.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Quoted 1 line

Which implies doubling every python3-* recipes, too.

I think that should only be for python3 packages which actually have binary builds.

Not just those. Script-only modules won't be found either by one build in the the other build's site-packages.

Am I getting this right: This is experimental, never worked and actually shouldn't even be in openembedded-core master at all? I'm trying to figure out if I'm wasting my time trying to make this work.

I have figured out what was needed, it wasn't that bad. I just sent two series for that, one for openembedded-core and one for meta-openembedded.

Some projects do not actually expect freethreading to be enabled, see the ones with moving the installed site-packages directory into the correct location:

+do_install:append () {
+    if [ ! -d ${D}${libdir}/${PYTHON_DIR} ]; then
+        mv ${D}${libdir}/python${PYTHON_BASEVERSION} ${D}${libdir}/${PYTHON_DIR} +    fi
+}

I expect a lot of fallouts in CI.

#15 lore raw
In reply to Böszörményi Zoltán
Quoted 35 lines · Böszörményi Zoltán

2026. 03. 23. 15:34 keltezéssel, Bartosz Golaszewski írta:

Quoted 18 lines
Quoted 15 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 3 lines

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644
@@ -47,7 +47,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
 
Quoted 8 lines

meta/recipes-devtools/python/python3_3.14.3.bb UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar" · line 53

Quoted 7 lines
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
   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.

Quoted 7 lines

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?

Bart

#16 lore raw

2026. 03. 23. 15:45 keltezéssel, Bartosz Golaszewski írta:

Quoted 34 lines · Böszörményi Zoltán
Quoted 33 lines

2026. 03. 23. 15:34 keltezéssel, Bartosz Golaszewski írta:

Quoted 18 lines
Quoted 15 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 3 lines

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644
@@ -47,7 +47,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
 
Quoted 8 lines

meta/recipes-devtools/python/python3_3.14.3.bb UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar" · line 53

Quoted 7 lines
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
    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.

Quoted 8 lines
Quoted 7 lines

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.

A message that is not in the archive (sent off-list or not yet received): [email protected]

#18 lore raw

2026. 03. 23. 15:40 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:

Quoted 35 lines

2026. 03. 23. 15:34 keltezéssel, Bartosz Golaszewski írta:

Quoted 20 lines
Quoted 17 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 3 lines

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.

meta/recipes-devtools/python/python3_3.14.3.bb +0 -0
index 7a1ad1e386..492f2f93f0 100644
@@ -47,7 +47,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
 

   CVE_PRODUCT = "python:python python_software_foundation:python cpython"

Quoted 7 lines
Quoted 6 lines
meta/recipes-devtools/python/python3_3.14.3.bb +1 -1
-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.

Quoted 6 lines

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.

Plus, this seems to be a long term project to enable freethreaded python because a lot of modules have status lines like this:

    "Programming Language :: Python :: Free Threading :: 1 - Unstable",

For now, I wouldn't recommend it, only for experimenting.

Quoted 31 lines
Quoted 14 lines

ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3-iniconfig_2.3.0.bb:do_prepare_recipe_sysroot) failed with exit code '1'
ERROR: python3-3.14.3-r0 do_package: QA Issue: python3:
Files/directories were installed but not shipped in any package:
   /usr/bin/python3.14
Please set FILES such that these items are packaged. Alternatively if
they are unneeded, avoid installing them or delete them within
do_install.
python3: 1 installed and not shipped files. [installed-vs-shipped]
ERROR: python3-3.14.3-r0 do_package: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in:
/home/brgl/workspace/yocto/python-freethreaded/build/tmp/work/x86-64-v3-poky-linux/python3/3.14.3/temp/log.do_package.2308607

Quoted 7 lines

ERROR: Task (/home/brgl/workspace/yocto/python-freethreaded/sources/openembedded-core/meta/recipes-devtools/python/python3_3.14.3.bb:do_package) failed with exit code '1'

The MAJMIN seems to be used for the executable as well and with this change, it's missing from FILES.

Bart

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#233739): https://lists.openembedded.org/g/openembedded-core/message/233739
Mute This Topic: https://lists.openembedded.org/mt/118277380/3617728
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-