From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Joseph Kogut <joseph.kogut@gmail.com>,
Guillaume William Brs <guillaume.bressaix@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH v5 2/3] package/python-scipy: bump to version 1.12.0
Date: Sat, 26 Oct 2024 17:55:54 +0200 [thread overview]
Message-ID: <20241026175554.0466d8c5@windsurf> (raw)
In-Reply-To: <20240917021332.3838579-2-james.hilliard1@gmail.com>
On Mon, 16 Sep 2024 20:13:31 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> License hash changed due to date update:
> https://github.com/scipy/scipy/commit/0ace7295322148d74932bee32b0647e29c38fc8a
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/python-scipy/python-scipy.hash | 6 +++---
> package/python-scipy/python-scipy.mk | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
I wanted to apply this one, independently of the python-numpy update.
When verifying if it built properly, the following defconfig:
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_PYTHON3=y
BR2_PACKAGE_PYTHON_SCIPY=y
# BR2_TARGET_ROOTFS_TAR is not set
failed on building... python-numpy:
output/build/python-numpy-1.25.0/numpy/meson.build:203:49: ERROR: Could not get pkg-config variable and no default provided for <PkgConfigDependency lapack: True None>
(I did not investigate)
But the same issue is visible here:
http://autobuild.buildroot.net/results/179/179167678095590816c8b5c7330e3d5f018de554/build-end.log
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-26 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 2:13 [Buildroot] [PATCH v5 1/3] package/python-numpy: bump to version 1.26.4 James Hilliard
2024-09-17 2:13 ` [Buildroot] [PATCH v5 2/3] package/python-scipy: bump to version 1.12.0 James Hilliard
2024-10-26 15:55 ` Thomas Petazzoni via buildroot [this message]
2024-10-26 21:16 ` James Hilliard
2024-09-17 2:13 ` [Buildroot] [PATCH v5 3/3] package/python-cython: bump to version 3.0.11 James Hilliard
2024-10-26 15:56 ` Thomas Petazzoni via buildroot
2024-10-26 15:44 ` [Buildroot] [PATCH v5 1/3] package/python-numpy: bump to version 1.26.4 Thomas Petazzoni via buildroot
2024-10-26 21:15 ` James Hilliard
2024-10-26 21:31 ` Thomas Petazzoni via buildroot
2024-10-26 21:56 ` James Hilliard
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=20241026175554.0466d8c5@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=guillaume.bressaix@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=james.hilliard1@gmail.com \
--cc=joseph.kogut@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