[Octave-bug-tracker] [bug #35114] Octave 3.5.90: mkoctfile fails to link against BLAS/LAPACK

[John W. Eaton]

Follow-up Comment #13, bug #35114 (project octave):

I don't see a reason to have all .oct files linked with all libraries that
Octave requires.  That would include fftw, fontconfig, opengl, HDF, X11
libraries, etc. that don't make sense for most .oct files.  In the past, when
we did have all .oct files linking to these libraries, it was a source of
confusion.  So I don't want to revert this change.

Linking may happen to succeed on some platforms without directly linking to
LAPACK (for example) because the linker doesn't complain about unresolved
symbols when creating shared libraries, and those symbols are later found to
already be available when the shared library is loaded in Octave.  Perhaps
there is some option to cause the link step to require symbols to be resolved
a the time the shared library is created, but I don't know what that is.

You can use something like


LAPACK_LIBS = `mkoctfile -p LAPACK_LIBS`
...
mkoctfile ... $(LAPACK_LIBS)


to link with the same libraries that Octave uses.


    _______________________________________________________

Reply to this item at:

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

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