On Thu, 2023-06-15 at 08:31 +0200, Fons Adriaensen wrote:
> This must be the most confusing advice I ever got :-)
Hi Fons,
I can't agree more. However...
> So what should I do if I want to keep cblas, lapack, numpy, scipy
> etc.. working ?
• rocketmouse@archlinux ~
$ pacman -Qi blas openblas blas-openblas blas64-openblas openblas64 | grep
Provides
Description : An optimized BLAS library based on GotoBLAS2 1.13 BSD
(Provides BLAS/CBLAS/LAPACK/LAPACKE system-wide)
Provides : blas=3.11.0 cblas=3.11.0 lapack=3.11.0 lapacke=3.11.0
Provides : None
Description : An optimized BLAS library based on GotoBLAS2 1.13 BSD
(Provides BLAS/CBLAS/LAPACK/LAPACKE system-wide)
Provides : blas=3.11.0 cblas=3.11.0 lapack=3.11.0 lapacke=3.11.0
Provides : blas64=3.11.0 cblas64=3.11.0 lapack64=3.11.0
lapacke64=3.11.0
Provides : None
$ pactree lapack
blas-openblas provides lapack
└─openblas
└─gcc-libs
└─glibc>=2.27
├─linux-api-headers>=4.10
├─tzdata
└─filesystem
└─iana-etc
• rocketmouse@archlinux ~
$ pactree scipy
python-scipy provides scipy
├─python-numpy
│ ├─blas-openblas provides cblas
│ │ └─openblas
│ │ └─gcc-libs
│ │ └─glibc>=2.27
│ │ ├─linux-api-headers>=4.10
│ │ ├─tzdata
│ │ └─filesystem
│ │ └─iana-etc
[snip]
You would have notice the provided dependencies by running "pacman -Si"
too.
Regards,
Ralf
