On Thu, Dec 21, 2023 at 7:47 PM Randy MacLeod <[email protected]> wrote:
> On 2023-11-28 4:26 a.m., Zoltan Boszormenyi via lists.openembedded.org > wrote: > > So it's not just Fedora, but Python 3.12 in general. > > Googling for problem with threads + fork reveals that > it is indeed an issue even in C / POSIX: only the thread > executing fork() will become part of the new process, > but not the main process starting the thread or any > other threads from the original process. > > The warning is justified, and apparently the issue > not occurring in bitbake with previous Python versions > is pure luck. > > FYI: Fixed in Fedora 39 if you update to get python-3.12.1-1 or later. > But this fixes it only for bitbake master, right? With bitbake 2.0 used in kirkstone I still see bitbake processes still running after the build is finished.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#192845): https://lists.openembedded.org/g/openembedded-core/message/192845 Mute This Topic: https://lists.openembedded.org/mt/102826186/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
