From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Guillaume W. Bres" <guillaume.bressaix@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v1 6/7] package/python-scikitlearn: new package
Date: Wed, 17 Aug 2022 12:54:07 +0200 [thread overview]
Message-ID: <20220817125407.024ae30f@windsurf> (raw)
In-Reply-To: <20220816143943.16142-6-guillaume.bressaix@gmail.com>
Hello Guillaume,
On Tue, 16 Aug 2022 16:39:42 +0200
"Guillaume W. Bres" <guillaume.bressaix@gmail.com> wrote:
> +PYTHON_SCIKITLEARN_VERSION = 1.1.1
> +PYTHON_SCIKITLEARN_SITE = $(call github,scikit-learn,scikit-learn,$(PYTHON_SCIKITLEARN_VERSION))
> +PYTHON_SCIKITLEARN_LICENSE = BSD-3-Clause
> +PYTHON_SCIKITLEARN_LICENSE_FILES = COPYING
> +PYTHON_SCIKITLEARN_SETUP_TYPE = setuptools
> +PYTHON_SCIKITLEARN_DEPENDENCIES = \
> + host-python-cython \
> + host-python-scipy \
Are you sure it needs host-python-scipy? What error do you get if you
don't have host-python-scipy?
From a quick glance at scikitlearn's setup.py script (at
https://github.com/scikit-learn/scikit-learn/blob/main/setup.py#L303),
I have the impression it only tries to import numpy and scipy at
build-time to verify that their version is correct.
Though it's true than then it does import numpy/scipy stuff:
# These commands require the setup from numpy.distutils because they
# may use numpy.distutils compiler classes.
from numpy.distutils.core import setup
# Monkeypatches CCompiler.spawn to prevent random wheel build errors on Windows
# The build errors on Windows was because msvccompiler spawn was not threadsafe
# This fixed can be removed when we build with numpy >= 1.22.2 on Windows.
# https://github.com/pypa/distutils/issues/5
# https://github.com/scikit-learn/scikit-learn/issues/22310
# https://github.com/numpy/numpy/pull/20640
from numpy.distutils.ccompiler import replace_method
from distutils.ccompiler import CCompiler
from sklearn.externals._numpy_compiler_patch import CCompiler_spawn
But the below part is to avoid build errors on Windows. Can you try to
patch this out?
> + python-joblib \
> + python-threadpoolctl
Are you sure these are needed at build-time? You marked them as
run-time dependencies in your Config.in file.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-17 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 14:39 [Buildroot] [PATCH v1 1/7] package/python-joblib: new package Guillaume W. Bres
2022-08-16 14:39 ` [Buildroot] [PATCH v1 2/7] package/python-threadpoolctl: " Guillaume W. Bres
2022-08-16 14:39 ` [Buildroot] [PATCH v1 3/7] package/lapack: host-python-scipy needs host-lapack Guillaume W. Bres
2022-08-16 14:39 ` [Buildroot] [PATCH v1 4/7] package/python-pybind: host-python-scipy needs host-python-pybind Guillaume W. Bres
2022-08-16 14:39 ` [Buildroot] [PATCH v1 5/7] package/python-scipy: add host-package Guillaume W. Bres
2022-08-16 14:39 ` [Buildroot] [PATCH v1 6/7] package/python-scikitlearn: new package Guillaume W. Bres
2022-08-17 10:54 ` Thomas Petazzoni via buildroot [this message]
2022-08-16 14:39 ` [Buildroot] [PATCH v1 7/7] support/testing: add python-scikitlearn test Guillaume W. Bres
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=20220817125407.024ae30f@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=guillaume.bressaix@gmail.com \
--cc=thomas.petazzoni@bootlin.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