Re: linking liboctave fails (lapack missing?)

[Jaroslav Hajek]

On Mon, Aug 17, 2009 at 6:41 PM, John W. Eaton<address@hidden> wrote:
> On 15-Aug-2009, Benjamin Lindner wrote:
>
> | Now for the undefined reference linker errors:
>
> I checked in some additional changes.  I will deal with the mkoctfile
> and octave-bug scripts/programs later, but is there anything that I
> missed for building libcruft, liboctave, liboctinterp, and the .oct
> files?
>

One possible gotcha is that building now fails if you have static
libraries, e.g suitesparse. The reason is that not all functions are
used from within liboctave, so not all are linked in (if using static
libs). Since SPARSE_LIBS are not specified again, you get undefined
references.

One possibility is to wrap the SPARSE_LIBS in -Wl,--whole-archive
-Wl, --no-whole-archive, or just switch to a shared library (which I'd
recommend anyway and I'm going to do it).

-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz