Re: octave

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Wed, Apr 06, 2016 at 09:32:30PM +0100, Patrick Welche wrote:
> As a workaround for PR 48272 I have been setting
> 
> PKGSRC_FORTRAN=gfortran
> 
> when building octave + blas and friends. I just tried octave 4 now that qt5
> seems to be happy, and with PKG_DEVELOPER=yes see:
> 
> => Checking for missing run-time search paths in octave-4.0.0nb1
> ERROR: bin/octave-cli-4.0.0: missing library: libgfortran.so.3
> ERROR: bin/octave-cli-4.0.0: missing library: libstdc++.so.6
> ERROR: libexec/octave/4.0.0/exec/x86_64--netbsd/octave-gui: missing library: libgfortran.so.3
> ERROR: libexec/octave/4.0.0/exec/x86_64--netbsd/octave-gui: missing library: libstdc++.so.6
> 
> $ ls /usr/pkg/gcc48/lib/libgf*
> /usr/pkg/gcc48/lib/libgfortran.a        /usr/pkg/gcc48/lib/libgfortran.so.3
> /usr/pkg/gcc48/lib/libgfortran.la       /usr/pkg/gcc48/lib/libgfortran.so.3.0
> /usr/pkg/gcc48/lib/libgfortran.so       /usr/pkg/gcc48/lib/libgfortran.spec
> 
> Am I expecting too much of e.g. libtool-fortran?

It's not the job of libtool-fortran to cleanup after the compiler.
Sadly, normal GCC behavior is to create broken binaries without correct
rpath unless explicitly patched.

Joerg