[Python-modules-team] Bug#914655: Bug#929296: libopenblas-base: is libopenblas.so needed?

Drew Parsons dparsons at debian.org
Tue May 21 13:08:36 BST 2019

On 2019-05-21 19:55, Mo Zhou wrote:
> On 2019-05-21 09:13, Drew Parsons wrote:
>> Perhaps our scipy build should explicitly avoid libopenblas.so by 
>> setting
>> export BLAS=/path/to/libblas.so
>> export LAPACK=/path/to/liblapack.so
>> as suggested at
>> http://scipy.github.io/devdocs/building/linux.html#specific-instructions
> Sounds good to me if exporting these environment variables solves the
> problem.
> But what happens during run time? Will scipy mix the usage of
> (libopenblas.so) and (libblas.so + liblapack.so) ?

I don't think so. Once its built and linked, it's got the NEEDED 
liblapack.so headers so no more fuss about libopenblas.so

It looks like there's something in the configuration pattern which 
explicitly checks for openblas and links to it if its found.  The weird 
things is there is no such explicit check in the scipy code. I wonder if 
it's grabbing some setup from numpy.  Digging further, by the look of it 
/usr/lib/python3/dist-packages/numpy/distutils/system_info.py is the 
root of the problem.


More information about the Python-modules-team mailing list