From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class
Date: Wed, 22 Mar 2023 09:18:44 +0100 [thread overview]
Message-ID: <aa1e32fb-dce8-826b-92a2-37f74c484989@gmail.com> (raw)
In-Reply-To: <39A18BD0-B6AD-4EF0-806B-578EDB2D3DC4@arm.com>
2023. 03. 20. 17:26 keltezéssel, Ross Burton írta:
> On 20 Mar 2023, at 15:01, Böszörményi Zoltán <zboszor@gmail.com> wrote:
>> 2023. 03. 20. 15:46 keltezéssel, Ross Burton írta:
>>> On 17 Mar 2023, at 07:25, Zoltan Boszormenyi via lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org> wrote:
>>>> +inherit setuptools3-base python3targetconfig python_pep517 meson-common
>>> I still don’t see why you need to split the meson class up.
>> See the other thread. For some reason, meson always wins
>> regardless of the inheritance order, so do_configure has
>> meson_do_configure instead of pep517_do_configure, etc.
> Add a new do_configure to your class which simply calls the right one.
It still doesn't work. meson_do_qa_configure fails with this:
ERROR: python3-meson-python-native-0.13.0.pre0-r0 do_configure: Error executing a python
function in exec_func_python() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:meson_do_qa_configure(d)
0003:
File:
'/data2/dtd-yocto-4.2/conf/../layers/openembedded-core/meta/classes-recipe/meson.bbclass',
lineno: 163, function: meson_do_qa_configure
0159:
0160:python meson_do_qa_configure() {
0161: import re
0162: warn_re = re.compile(r"^WARNING: Cross property (.+) is using default value
(.+)$", re.MULTILINE)
*** 0163: with open(d.expand("${B}/meson-logs/meson-log.txt")) as logfile:
0164: log = logfile.read()
0165: for (prop, value) in warn_re.findall(log):
0166: bb.warn("Meson cross property %s used without explicit assignment,
defaulting to %s" % (prop, value))
0167:}
Exception: FileNotFoundError: [Errno 2] No such file or directory:
'/data2/dtd-yocto-4.2/tmp-sicom-glibc/work/x86_64-linux/python3-meson-python-native/0.13.0.pre0-r0/build/meson-logs/meson-log.txt'
ERROR: Logfile of failure stored in:
/data2/dtd-yocto-4.2/tmp-sicom-glibc/work/x86_64-linux/python3-meson-python-native/0.13.0.pre0-r0/temp/log.do_configure.3235105
ERROR: Task
(virtual:native:/data2/dtd-yocto-4.2/conf/../layers/meta-sicom/recipes-support/python3/python3-meson-python_0.13.0.pre0.bb:do_configure)
failed with exit code '1'
Naturally, as running meson's configure stage went from
do_configure to do_compile indirectly via "nativepython3 -m build ..."
Sorry, there seems to be no way around it but splitting out the
environment setup from meson.bbclass into meson-common class.
If you don't like the "-common" naming, I can rename it to
meson-env.bbclass or something like that.
I will still rework python3-meson-python to not require
the dummy patchelf python module and review other
comments and make necessary changes.
Thanks.
next prev parent reply other threads:[~2023-03-22 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 7:25 [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class Zoltán Böszörményi
2023-03-17 7:25 ` [meta-python][PATCH v2 2/4] python3-patchelf: New recipe Zoltán Böszörményi
2023-03-20 16:09 ` [oe] " Ross Burton
2023-03-17 7:25 ` [meta-python][PATCH v2 3/4] python3-pyproject-metadata: " Zoltán Böszörményi
2023-03-20 14:45 ` [oe] " Ross Burton
2023-03-17 7:25 ` [meta-python][PATCH v2 4/4] python3-meson-python: " Zoltán Böszörményi
2023-03-20 14:52 ` [oe] " Ross Burton
2023-03-20 14:46 ` [oe] [meta-python][PATCH v2 1/4] python_mesonpy.bbclass: New class Ross Burton
2023-03-20 15:01 ` Böszörményi Zoltán
2023-03-20 16:26 ` Ross Burton
2023-03-22 8:18 ` Böszörményi Zoltán [this message]
[not found] ` <174EAFE93556A78F.19937@lists.openembedded.org>
2023-03-23 11:18 ` Böszörményi Zoltán
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=aa1e32fb-dce8-826b-92a2-37f74c484989@gmail.com \
--to=zboszor@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-devel@lists.openembedded.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.