From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@busybox.net, ralf.gommers@gmail.com,
Guillaume Bres <guillaume.bressaix@gmail.com>
Subject: Re: [Buildroot] [RFC v3 2/2] package/python-scipy: bump version to 1.9.0
Date: Mon, 8 Aug 2022 23:13:02 +0200 [thread overview]
Message-ID: <20220808231302.08adad89@windsurf> (raw)
In-Reply-To: <28767d03-5c5f-d40e-12d1-ebdc6b3a5900@mind.be>
On Mon, 8 Aug 2022 22:58:46 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> pybind is consistently annoying, it uses ldd and stuff to discover paths...
Well, it's not just pybind. Python itself, in its ctype.find_library()
function, uses ldconfig, tries to use gcc on the target, and more funky
stuff that borks terribly in a Buildroot situation.
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-08 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 14:36 [Buildroot] [RFC v3 1/2] package/pkg-meson.mk: support fortran cross-compilation Guillaume W. Bres
2022-08-05 14:36 ` [Buildroot] [RFC v3 2/2] package/python-scipy: bump version to 1.9.0 Guillaume W. Bres
2022-08-05 14:46 ` Guillaume Bres
2022-08-08 20:58 ` Arnout Vandecappelle
2022-08-08 21:13 ` Thomas Petazzoni via buildroot [this message]
2022-08-09 8:37 ` Guillaume Bres
2022-08-27 9:11 ` Guillaume Bres
[not found] ` <CABL7CQjFbqaDd2ULBsPVyKM3cAEjCSHEdnY9vfxA=VMuRbdNjg@mail.gmail.com>
2022-09-01 19:43 ` Guillaume Bres
2022-08-06 22:13 ` [Buildroot] [RFC v3 1/2] package/pkg-meson.mk: support fortran cross-compilation Thomas Petazzoni via buildroot
2022-08-08 19:47 ` Yann E. MORIN
2022-08-09 16:25 ` Yann E. MORIN
2023-06-26 21:34 ` 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=20220808231302.08adad89@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=buildroot@busybox.net \
--cc=guillaume.bressaix@gmail.com \
--cc=ralf.gommers@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 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.