On Tue, Nov 12, 2013 at 02:40:42PM -0800, Steve Kargl wrote:
> On Tue, Nov 12, 2013 at 10:19:46PM +0100, Tijl Coosemans wrote:
> > On Tue, 12 Nov 2013 12:19:22 -0800 Steve Kargl wrote:
> > > This can't be good. And, unfortunately, testing math/octave shows
> > > no better :(
> > >
> > > % octave
> > > Segmentation fault (core dumped)
> > > % ldd /usr/local/bin/octave-3.6.4 | grep ++
> > > libstdc++.so.6 => /usr/local/lib/gcc46/libstdc++.so.6
> > > (0x3c92ec000)
> > > libc++.so.1 => /usr/lib/libc++.so.1 (0x3c9801000)
> > This could be because you enabled the OPENMP option in math/fftw3.
> Unfortuantely, that's not it. Just rebuilt fftw3 and octave still
> dies. ldd shows that /usr/local/lib/octave/3.6.4/liboctinterp.so.1
> is bringing in both libc++ and libstdc++, but it is also linked
> to 52 other libraries.
What a rabbit hole FreeBSD has dug!
Needed to recompile fltk, libGL, and libGLU with USE_GCC=any in
their Makefile to eliminate octave's dependence on libc++.
Octave now will start as expected. Guess I need to chase down
other ports that may use fltk, libGL, and/or libGLU to ensure
the new installation does not cause a new libc++ vs libstdc++
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"