From owner-freebsd-current@FreeBSD.ORG Sat Nov 16 16:55:05 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1D30400; Sat, 16 Nov 2013 16:55:05 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9006829EB; Sat, 16 Nov 2013 16:55:05 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id rAGGsuEA037253; Sat, 16 Nov 2013 08:54:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id rAGGstL1037252; Sat, 16 Nov 2013 08:54:55 -0800 (PST) (envelope-from sgk) Date: Sat, 16 Nov 2013 08:54:55 -0800 From: Steve Kargl To: Tijl Coosemans Subject: Re: Are clang++ and libc++ compatible? Message-ID: <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> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131116135811.23b00fa3@kalimero.tijl.coosemans.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org, gerald@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 16:55:05 -0000 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. -- Steve