[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #45659] version function: options and return v

From: Martin K
Subject: [Octave-bug-tracker] [bug #45659] version function: options and return values supported by Matlab
Date: Mon, 5 Feb 2018 10:47:50 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0

Follow-up Comment #42, bug #45659 (project octave):

I talked to @CH today about this issue because he thinks I know something. 

The technical reason what happens, to link a application against OpenBLAS and
ATLAS, is described in
or http://www.netlib.org/lapack/lawnspdf/lawn284.pdf and appears in the case
of Octave because the configure script prefers to use libopenblas with not
"--with-blas" argument is given. But several depending libraries (like arpack,
suitesparse, qrupdate) used from the system are linked against libblas. If the
OS is debian/ubuntu this is set by update-alternatives to one of the BLAS
libraries installed. In the case of @mmuetzel this is ATLAS. This causes both
libraries with the same symbols to be linked against Octave and nobody can say
which symbol is called in which situation.  In order to avoid this and make
the idea of check_blas_ver.cc properly working, the configure script should
search by default for libblas.so and liblapack.so instead of libopenblas.so
and during the startup of octave one should search like the check_blas_ver.cc
idea for different characteristic symbols from the BLAS libraries and drop a
warning if octave is linked against more than one BLAS implementation. 

Can you check against which BLAS Octave is linked using ldd `which octave-cli`


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]