From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tim Orling <ticotimo@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/4] python3-numpy: inherit python_mesonpy
Date: Tue, 20 Feb 2024 11:33:01 +0000 [thread overview]
Message-ID: <9ce2c246e5de18f1ce8fe2c81d42c20a3f87b480.camel@linuxfoundation.org> (raw)
In-Reply-To: <c57f8a02b11dd08758cb9881ae82db985dbe5ee4.1708363628.git.tim.orling@konsulko.com>
On Mon, 2024-02-19 at 09:30 -0800, Tim Orling wrote:
> Replace the deprecated setuptools3 bbclass with python_mesonpy.
>
> The build-backend has been defined as "mesonpy" since:
> https://github.com/numpy/numpy/commit/942fb8caf33a65e449fbf198ecf1cd39be953248
>
> The vendored meson-python was dropped in:
> https://github.com/numpy/numpy/commit/6544e33ac7a3a600c2fb565401c811a17ecdb3d5
>
> While we are at it:
> * Drop ${PYTHON_PN} and use python3 instead
> * Sort RDEPENDS alphabetically
>
> The ptests run, but we still have issues with sufficient memory and
> free disk space (the reason python3-numpy is in PTEST_PROBLEMS).
>
> Signed-off-by: Tim Orling <tim.orling@konsulko.com>
This looks to introduce a reproducibility issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4399
Cheers,
Richard
next prev parent reply other threads:[~2024-02-20 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:30 [PATCH 0/4] Add python_mesonpy ("mesonpy") PEP-517 backend support Tim Orling
2024-02-19 17:30 ` [PATCH 1/4] python3-meson-python: move from meta-python Tim Orling
2024-02-19 17:30 ` [PATCH 2/4] python_mesonpy.bbclass: " Tim Orling
2024-02-19 17:30 ` [PATCH 3/4] python3-numpy: inherit python_mesonpy Tim Orling
2024-02-20 11:33 ` Richard Purdie [this message]
2024-02-20 18:10 ` [OE-core] " Trevor Gamblin
2024-02-19 17:30 ` [PATCH 4/4] recipetool; add support for python_mesonpy class Tim Orling
2024-02-19 17:54 ` Patchtest results for " patchtest
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=9ce2c246e5de18f1ce8fe2c81d42c20a3f87b480.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.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