o be specific and
fail early if the configured choice is not available in the build
environment. Pkgsrc is especially trying hard to avoid locating
libraries from the host system (possibly a full GNU/Linux distro) if
not explicitly told to.
Also, my H
could link the vendored
superly with -lblas without changing the meson machinery?
Alrighty then,
Thomas
--
Dr. Thomas Orgis
HPC @ Universität Hamburg
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-di
Am Sun, 3 Dec 2023 19:54:10 +0100
schrieb "Dr. Thomas Orgis" :
> > You have to go through a "build frontend" to produce a wheel, which then
> > gets installed/repackaged for your distro.
>
> This is obviously happening in pkgsrc.
>
> I'll
x27;])
So there's this elaborate machinery that special-cases BLAS as a
library that could (not) offer certain sets of API? Well, as long as
the dynamic libcblas is used, the base BLAS API should be transparently
avaible and those meson tests will work … ?
I'll do some testing tomorro
9' but uses
feature introduced in '1.3.0': dep 'blas' custom lookup.
--
Dr. Thomas Orgis
HPC @ Universität Hamburg
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le.
ild if a 64 variant is chosen by the user. I wonder a bit if there
are possible pitfalls combining other libraries with Python and
indirectly some incompatible BLAS variant via NumPy … but one point of
our user choice is that they could ensure that all packages really use
the same BLAS.
Alrighty t
