Re: linking liboctave fails (lapack missing?)

[John W. Eaton]

On 13-Aug-2009, Benjamin Lindner wrote:

| Benjamin Lindner wrote:
| > Benjamin Lindner wrote:
| >> Hello,
| >>
| >> I just tried to build the recent development tip on mingw32 and 
| >> building fails at linking liboctave with a phletora of missing symbols 
| >> from the lapack library.
| >>
| >> looking at the linker command I see that indeed there is no -llapack 
| >> present.
| >>
| >> Digging the changelog I find that at revision 9490:3aeb7d881578
| >> $(BLAS_LIBS) has been removed from LINK_DEPS in liboctave/makefile.in
| >>
| >> I guess it should still be there, since arpack, qrupdate and quite 
| >> some octave code depends on it.
| >>
| > 
| > I see that there is already a thread covering this topic on the bugs 
| > list. Sorry for the double-post.
| > 
| > Hovever, liboctave directly uses functinos from lapack, and uses the 
| > qrupdate and qrpack library which both depend on lapack, so lapack 
| > *should* be listed in LINK_DEPS.
| > 
| 
| The attached changeset fixes the linker issues for mingw32 platform by 
| adding $(BLAS_LIBS) in liboctave's link depencendies.

I made this change.

It would be helpful if people building Octave on Windows and OS X
systems could configure and build the latest Octave sources on and
send a list of symbols that are unresolved when creating the libcruft,
liboctave, liboctinterp shared libraries, when linking the Octave
executable file, and when building the .oct files.

When building the liboctinterp shared library, is it necesary to
explicitly list all of the libraries that are linked with liboctave?
Or are only some required, and if so, which ones, and why only those?

Thanks,

jwe