From: "Gregory Anders" <greg@gpanders.com>
To: Jack Mitchell <ml@embed.me.uk>
Cc: zboszor@pr.hu, Khem Raj <raj.khem@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Upstream scipy recipe to meta-openembedded
Date: Tue, 13 Jul 2021 13:09:18 +0000 [thread overview]
Message-ID: <YO2QfsrtVgrsw7YX@gpanders.com> (raw)
In-Reply-To: <e025ca46-c030-978f-3ec0-499df2ba14a6@embed.me.uk>
On Tue, 13 Jul 2021 11:46 +0100, Jack Mitchell wrote:
>On 13/07/2021 11:20, Zoltan Boszormenyi via lists.openembedded.org wrote:
>>
>> FYI, there's another layer
>> (https://github.com/tuxable-ltd/meta-scikit-learn that
>> I had to fork and make hardknott-compatible) that uses python3-scipy as
>> a build
>> and runtime dependency for python3-scikit-learn so import
>> sklearn.linear_model"
>> is possible. That layer also extends python3-scipy with a native build
>> variant
>> which doesn't exist in your layer AND patches lapack further to use
>> openblas.
>
>Yes, that would be my layer. I had never intended to upstream the
>scikit-learn portions as I don't believe it is maintainable in a generic
>layer due to the niche use-cases and awkwardness of the build system
>itself and it's dependencies, in addition to the very large build time
>which would put strain on auto-builders.
>
>What I had intended to do though, which I haven't got round to yet is
>try to provide a virtual provider for blas/cblas in meta-oe which would
>allow openblas to be properly upstreamed and then packageconfigs and
>preferred versions used for selection as distro policy.
>
Thanks, I wasn't aware of this project. And it looks like you actually
sent a PR to my meta-scipy layer at one point, so thank you!
Jack, would you mind if I simply directed people from my meta-scipy
repository to your meta-scikit-learn layer? I am no longer using scipy
in OE so maintaining this layer (e.g. testing contributions and updating
for new versions) is falling behind.
If not then that is totally fine, I will just add a call for a new
maintainer.
Thanks,
Greg
next prev parent reply other threads:[~2021-07-13 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 15:19 Upstream scipy recipe to meta-openembedded Gregory Anders
2021-07-12 16:01 ` [oe] " Khem Raj
2021-07-13 10:20 ` Zoltan Boszormenyi
2021-07-13 10:46 ` Jack Mitchell
2021-07-13 13:09 ` Gregory Anders [this message]
2021-07-15 8:44 ` Jack Mitchell
2021-07-15 13:08 ` Gregory Anders
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=YO2QfsrtVgrsw7YX@gpanders.com \
--to=greg@gpanders.com \
--cc=ml@embed.me.uk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=zboszor@pr.hu \
/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.