From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Bartosz Golaszewski <brgl@kernel.org>,
Trevor Gamblin <tgamblin@baylibre.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH 13/13] libxcb: inherit python3native
Date: Thu, 26 Mar 2026 14:47:36 +0100 [thread overview]
Message-ID: <3e1d449f-a5f9-477e-9acb-437a8f7837ab@gmail.com> (raw)
In-Reply-To: <18A0671344EE5B33.57592@lists.openembedded.org>
2026. 03. 26. 14:26 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:
> 2026. 03. 26. 14:06 keltezéssel, Alexander Kanavin írta:
>> On Thu, 26 Mar 2026 at 13:51, Zoltan Boszormenyi via
>> lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org>
>> wrote:
>>> Instead of open coding, use python3native and xcb-proto-native
>>> as an extra build dependency.
>>> -DEPENDS = "xcb-proto xorgproto libxau libpthread-stubs libxdmcp"
>>> +DEPENDS = "xcb-proto-native xcb-proto xorgproto libxau libpthread-stubs libxdmcp"
>> This change isn't explained.
>
> I will move this commit to the free-threading enablement RFC series and
> add the explanation to the commit message.
>
> The problem is that the build failed with ModuleNotFoundError
> for xcbgen when free-threading was enabled.
> No idea how this is satisfied without the xcb-proto installed on the host.
Now I know. This change won't be necessary, but another tweak for xcb-proto will be.
The xcb-proto.pc must be generated correctly with the ABI flag.
>>> -inherit autotools pkgconfig features_check
>>> +inherit autotools pkgconfig python3native features_check
>>> -export PYTHON = "python3"
>> I'm not sure this is an improvement? We try to avoid using native
>> python whenever possible, and use python from the host if it doesn't
>> cause issues.
>>
>> The rest of the patchset looks okay on first glance, but it does
>> include a breaking change, and you need to at least try to fix meta-oe
>> (or ensure nothing breaks in there which is unlikely).
>>
>> Alex
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#234001): https://lists.openembedded.org/g/openembedded-core/message/234001
> Mute This Topic: https://lists.openembedded.org/mt/118517418/3617728
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [zboszor@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2026-03-26 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:42 Use PYTHON_DIR consistently Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 01/13] python3: Add warning comment before PACKAGECONFIG[freethreading] Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 02/13] python3-dir.bbclass: Move PYTHON_ABI into PYTHON_DIR Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 03/13] python3: Use the variables from python3-dir.bbclass Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 04/13] python3native.bbclass: Stop using PYTHON_ABI Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 05/13] python_pyo3.bbclass: Pass ABI flag and use PYTHON_MAINVERSION Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 06/13] clang: Use PYTHON_MAINVERSION for python module versioning Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 07/13] gdb, gdb-cross-canadian: Stop using PYTHON_ABI Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 08/13] boost: " Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 09/13] lttng-tools: " Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 10/13] lttng-ust: " Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 11/13] libcap-ng-python: Use PYTHON_DIR for FILES Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 12/13] hwlatdetect: Use PYTHON_DIR Zoltán Böszörményi
2026-03-26 12:42 ` [PATCH 13/13] libxcb: inherit python3native Zoltán Böszörményi
2026-03-26 13:06 ` [OE-core] " Alexander Kanavin
2026-03-26 13:26 ` Böszörményi Zoltán
[not found] ` <18A0671344EE5B33.57592@lists.openembedded.org>
2026-03-26 13:47 ` Böszörményi Zoltán [this message]
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=3e1d449f-a5f9-477e-9acb-437a8f7837ab@gmail.com \
--to=zboszor@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=brgl@kernel.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tgamblin@baylibre.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