[Octave-bug-tracker] [bug #49547] Update libs blas and lapack

[Ll]

Follow-up Comment #6, bug #49547 (project octave):

Hi, Thx for your help, reading and experimenting i found some things, and the
solution, first is a system problem, but has 2 problems:

1) Some libs don't was rebuilt with LAPACK and BLAS changed versions.

2) Octave use BLAS and LAPACK directly, but when exist the above problem we
get an error, basically can't found the actual libs, its like is trying to
search the libs in the broken depends paths.

So with this in mind to solve this at least in gentoo we can use:

revdep-rebuild


For the systems do not build their own libs is necessary send a bug report to
rebuild the libs.

I think part of this is done, i would like check the second point, of how
octave get libs path to finish this.

Mike do you know how octave does this?


Only as a note, in the bug https://savannah.gnu.org/bugs/?42760
they said octave wasn't using BLAS and LAPACK directly, but i confirm is using
it, so testing and searching direct dependencies of libs this files of octave
use it:


/usr/lib64/octave/4.3.0+/liboctave.so
/usr/lib64/octave/4.3.0+/liboctave.so.4
/usr/lib64/octave/4.3.0+/liboctave.so.4.0.0
/usr/lib64/octave/4.3.0+/liboctgui.so
/usr/lib64/octave/4.3.0+/liboctgui.so.2
/usr/lib64/octave/4.3.0+/liboctgui.so.2.0.0
/usr/lib64/octave/4.3.0+/liboctinterp.so
/usr/lib64/octave/4.3.0+/liboctinterp.so.4
/usr/lib64/octave/4.3.0+/liboctinterp.so.4.0.0
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__delaunayn__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__eigs__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__fltk_uigetfile__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__glpk__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__init_fltk__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__init_gnuplot__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__osmesa_print__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/__voronoi__.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/amd.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/audiodevinfo.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/audioread.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/ccolamd.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/chol.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/colamd.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/convhulln.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/dmperm.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/fftw.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/gzip.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/qr.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/symbfact.oct
/usr/lib64/octave/4.3.0+/oct/x86_64-pc-linux-gnu/symrcm.oct


We can found direct dependencies with objdump -x if you try ldd you will get a
recursion dependence.


If you need found the broken libs you can follow this:
first search broken libs
In cli

ldd -v /usr/bin/octave

for gui

ldd -v /usr/libexec/octave/4.3.0+/exec/x86_64-pc-linux-gnu/octave-gui


in the log you will can see something like "not found" with broken libs, and
it will say what libs depends of it, so then you need search what package
files belongs and send the bug report.

Thx. Cya.

    _______________________________________________________

Reply to this item at:

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

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