Date: Tue, 12 Nov 2013 15:13:34 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Tijl Coosemans <tijl@coosemans.org> Cc: Dimitry Andric <dim@FreeBSD.org>, freebsd-current@FreeBSD.org, David Chisnall <theraven@FreeBSD.org> Subject: Re: Are clang++ and libc++ compatible? Message-ID: <20131112231334.GA5188@troutmask.apl.washington.edu> In-Reply-To: <20131112224042.GA5050@troutmask.apl.washington.edu> References: <20131112163219.GA2834@troutmask.apl.washington.edu> <77CB2B92-216A-4C80-B033-7E582B5F0DFC@FreeBSD.org> <20131112165422.GA2939@troutmask.apl.washington.edu> <E0FE40D9-726C-4501-B31A-3622510C1C68@FreeBSD.org> <20131112175556.GA3319@troutmask.apl.washington.edu> <20131112201922.GA4330@troutmask.apl.washington.edu> <20131112221946.78602db0@kalimero.tijl.coosemans.org> <20131112224042.GA5050@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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++ conflict. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131112231334.GA5188>