octave3-0-headers gives the wrong library directories for gfortran

[Paul Novotny]

Binary package hint: octave3.0-headers

Release: intrepid amd64
Package: octave3.0-headers (1:3.0.1-6ubuntu1)

When compiling a cc file with mkoctfile I get the following:

/usr/bin/ld: cannot find -lgfortranbegin
collect2: ld returned 1 exit status

This is because in /usr/include/octave/oct-conf.h has the following line:

#define OCTAVE_CONF_FLIBS "-L/usr/lib/gcc/x86_64-linux-gnu/4.3.1 -L/usr/lib/gcc/x86_64-linux-gnu/4.3.1/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.3.1/../../.. -lhdf5 -lz -lgfortranbegin -lgfortran -lm"

On my machine (intrepid amd64), there is no /usr/lib/gcc/x86_64-linux-gnu/4.3.1 directory or no link to /usr/lib/gcc/x86_64-linux-gnu/4.3. Adding a softlink from /usr/lib/gcc/x86_64-linux-gnu/4.3.1 to /usr/lib/gcc/x86_64-linux-gnu/4.3 solves the problem.

Or, correcting oct-conf.h to look in 4.3.2 would also solve the problem.

[Rebecca Palmer (rebecca-palmer)]

Could you post a .cc file that triggers this bug? My amd64 Intrepid also has this apparently broken link, but compiles Octave-Forge packages from source (including arpack, which is a binding for a Fortran library) without this problem.

[Paul Novotny (paul-novotny)]

Here is the .cc file that gave me the error above. BTW, I compiled it with the following command:

mkoctfile -DHAVE_CONFIG_H __convn__.cc

[Rebecca Palmer (rebecca-palmer)]

Appears to be fixed in Jaunty: oct-conf.h now points to 4.3.3, where the libraries in question do exist, and this file now compiles without error.