Re: linking liboctave fails (lapack missing?)

[Michael Goffioul]

On Fri, Aug 14, 2009 at 3:12 PM, John W. Eaton<address@hidden> wrote:
> 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?

Under Windows, usually you only need to list the libraries whose
symbols are actually used in the target library. If the target library
does not reference any symbol from a dependent lib, even if this
dependent lib is required by another dependent lib, it does not
need to be listed.

Michael.