Date: Sat, 16 Nov 2013 18:14:47 +0100 From: Tijl Coosemans <tijl@coosemans.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@FreeBSD.org, gerald@FreeBSD.org Subject: Re: Are clang++ and libc++ compatible? Message-ID: <20131116181447.5e9eada4@kalimero.tijl.coosemans.org> In-Reply-To: <20131116165455.GA37237@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> <20131116135811.23b00fa3@kalimero.tijl.coosemans.org> <20131116165455.GA37237@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Nov 2013 08:54:55 -0800 Steve Kargl wrote: > On Sat, Nov 16, 2013 at 01:58:11PM +0100, Tijl Coosemans wrote: >> On Tue, 12 Nov 2013 14:40:42 -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. >> >> USE_FORTRAN=yes currently implies USE_GCC=yes so the C++ code in >> math/octave links with libstdc++ while dependencies link with libc++. >> Gerald, is it possible to separate USE_FORTRAN from USE_GCC? > > This isn't the problem. gfortran does not pull libstdc++.so into > the build. As pointed out in another email, libGL, libGLU, fltk, > and libgraphite2 all were linked to libc++ and libstdc++. Recompiling > those ports with USE_GCC=any, fixed octave. The math/octave Makefile has USE_FORTRAN=yes (FC=gfortran46). This currently implies USE_GCC=yes (CC=gcc46, CXX=g++46) which pulls in libstdc++. If this could be changed (i.e. FC=gfortran46, CC=cc, CXX=c++) you would not have to add USE_GCC to the dependencies.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131116181447.5e9eada4>