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

[Markus Mützel]

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

Martin, thank you for the explanation.
Here is part of the output of ldd on the octave-cli in src/.lib of my build
tree:

        liblapack.so.3 => /usr/lib/x86_64-linux-gnu/liblapack.so.3
(0x00007f5d981d8000)
        libblas.so.3 => /usr/lib/x86_64-linux-gnu/libblas.so.3 
(0x00007f5d95b4c000)
        libopenblas.so.0 => /usr/lib/x86_64-linux-gnu/libopenblas.so.0
(0x00007f5d8f753000)


Also the version of Octave that is shipped with Ubuntu (apt-get) seems to be
linked with BLAS and OpenBLAS:

        liblapack.so.3 => /usr/lib/x86_64-linux-gnu/liblapack.so.3
(0x00007f5a3d077000)
        libblas.so.3 => /usr/lib/x86_64-linux-gnu/libblas.so.3 
(0x00007f5a3a9eb000)
        libopenblas.so.0 => /usr/lib/x86_64-linux-gnu/libopenblas.so.0
(0x00007f5a345f2000)


Does this mean we could have trouble?

Strange thing though, I can't find any line in the output of ldd referencing
"libatlas". Yet I can call ATL_buildinfo from an .oct file without
specifically linking to it and "ATL_sgemm" is found in the loaded symbols.
Unless mkoctfile links ATLAS automatically if configure finds it?
In my config.log I see:

  BLAS libraries:                -lcblas -lf77blas -latlas



Wrt checking the linked BLAS implementations: Do you know any specific symbol
that can be used to identify reference BLAS (i.e. one that isn't present in
the other BLASs)?

    _______________________________________________________

Reply to this item at:

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

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