[Octave-bug-tracker] [bug #45659] version function: options and return values supported by Matlab

[Martin K]

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

@mmuetzel 
I installed Octave 4.2.1 using apt on a clean Ubuntu 17.10 system an ran into
the same problem. It installs by default OpenBLAS as LAPACK and as BLAS
implementation but with a strange behavior to satisfy the update-alternative
system. Afterwards I got the following setup:

-> libblas.so.3 is provided by OpenBLAS ( Symlink to
/usr/lib/x86_64-linux-gnu/openblas/libblas.so.3) 
-> liblapack.so.3 is provides by OpenBLAS ( Symlink to
/usr/lib/x86_64-linux-gnu/openblas/liblapack.so.3) but links to 
/usr/lib/x86_64-linux-gnu/libopenblas.so.0 

This setup is ok as long libblas.so and liblapack.so are provided by the same
version of OpenBLAS. If for example libblas.so.3 is changed by 

apt install libatlas3-base
update-alternatives --set libblas.so.3-x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/atlas/libblas.so.3


then the BLAS implementations get mixed and you can find ATLAS and OpenBLAS
symbols although Octave is linked correctly against libblas.so and
liblapack.so 

The characteristic symbols are really a problem. 
Some stuff I know: 
- OpenBLAS: something from the openblas_get_config
- GotoBLAS: gotoblas_... but not openblas_ 
- ATLAS: ATL_buildinfo
- Reference: Nothing
- MKL: mkl_... 
- ACML: acmlinfo
- FlexiBLAS: flexiblas_get_version and others depending on the loaded
backend.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45659>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/