From: "Javier Tia" <javier.tia@linaro.org>
To: "Martin Jansa" <martin.jansa@gmail.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: docs@lists.yoctoproject.org,
"Mikko Rapeli" <mikko.rapeli@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Re: [docs] [PATCH] Set max supported Python version
Date: Tue, 24 Dec 2024 17:38:59 -0600 [thread overview]
Message-ID: <031a8378-b9a0-4bf9-aab7-8b98517f6779@app.fastmail.com> (raw)
In-Reply-To: <CA+chaQcQN96LXQGKuP_MR1AO+ROvWZrAyMCci=F8E1xJWOQA-Q@mail.gmail.com>
Hi Martin,
On Tue, Dec 24, 2024, at 5:34 PM, Martin Jansa wrote:
> FWIW: I'm using gentoo with 3.13.1 and I'm not seeing these issues
> since pseudo was updated.
Yes, I updated pseudo [1], but all build issues happened:
[1] bitbake pseudo-native -c cleanall && bitbake pseudo-native.
Thanks,
> On Wed, Dec 25, 2024 at 12:22 AM Richard Purdie via
> lists.yoctoproject.org
> <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
>>
>> On Tue, 2024-12-24 at 17:13 -0600, Javier Tia wrote:
>> > On Tue, Dec 24, 2024, at 4:54 PM, Richard Purdie wrote:
>> > > On Tue, 2024-12-24 at 16:16 -0600, Javier Tia via
>> > > lists.yoctoproject.org wrote:
>> > > > When Bitbake is used with Python 3.13, it generates numerous
>> > > > build
>> > > > issues that do not occur with Python 3.12. The documentation is
>> > > > clear
>> > > > for the supported Linux distributions, but not for the supported
>> > > > Python
>> > > > versions.
>> > > >
>> > > > Signed-off-by: Javier Tia <javier.tia@linaro.org>
>> > >
>> > > Can you be specific about which version of bitbake you saw the
>> > > issues
>> > > with? I was hoping we had resolved most of the issues with 3.13, at
>> > > least in master. We do aim to work with new versions of python but
>> > > it
>> > > obviously takes time to catch up and for fixes to make older
>> > > versions.
>> >
>> > With Bitbake from poky master (284a08b6e40761f) and BitBake from the
>> > latest master (c9906bb289dcfd9). Python 3.13.1.
>> >
>> > Issues:
>> >
>> > - "ERROR: ParseError in None: Not all recipes parsed, parser thread
>> > killed/died? Exciting." I noticed it was solved in Yocto Bugzilla,
>> > but I reopened the bug because I believe it is still not fixed.
>> >
>> > - The problem mentioned on
>> > https://wiki.yoctoproject.org/wiki/Pseudo_Abort with several poky
>> > recipes (base-files, update-rc.d, qemu, and u-boot) and other recipes
>> > from other layers.
>> >
>> > Please let me know if more information is needed.
>>
>> We have a fedora41 worker in the autobuilder cluster which has:
>>
>> fedora41-vk-1:~$ python3 --version
>> Python 3.13.0
>>
>> As you can see here:
>>
>> https://valkyrie.yoctoproject.org/#/workers/54
>>
>> is it running builds successfully. There is therefore some difference
>> in your environment and I'm not sure it is python 3.13 that is the
>> cause of the problems you're seeing.
>>
>> Are there any tracebacks in bitbake-cookerdaemon.log? Which distro is
>> this?
>>
>> The pseudo aborts are likely a different problem with a missing libc
>> intercept or similar issue and secondary to the other problem.
>>
>> Cheers,
>>
>> Richard
--
» Javier Tia ✍
next prev parent reply other threads:[~2024-12-24 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 22:16 [PATCH] Set max supported Python version Javier Tia
2024-12-24 22:54 ` [docs] " Richard Purdie
2024-12-24 23:13 ` Javier Tia
2024-12-24 23:22 ` Richard Purdie
2024-12-24 23:34 ` Martin Jansa
2024-12-24 23:38 ` Javier Tia [this message]
2024-12-24 23:47 ` Martin Jansa
2024-12-25 0:56 ` Javier Tia
2024-12-25 1:02 ` Javier Tia
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=031a8378-b9a0-4bf9-aab7-8b98517f6779@app.fastmail.com \
--to=javier.tia@linaro.org \
--cc=docs@lists.yoctoproject.org \
--cc=ilias.apalodimas@linaro.org \
--cc=martin.jansa@gmail.com \
--cc=mikko.rapeli@linaro.org \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.