From owner-freebsd-current@FreeBSD.ORG  Sat Nov 16 12:58:23 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 637A14E8;
 Sat, 16 Nov 2013 12:58:23 +0000 (UTC)
Received: from mailrelay002.isp.belgacom.be (mailrelay002.isp.belgacom.be
 [195.238.6.175])
 by mx1.freebsd.org (Postfix) with ESMTP id CF2512FAE;
 Sat, 16 Nov 2013 12:58:22 +0000 (UTC)
X-Belgacom-Dynamic: yes
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnYGAGprh1Jbs6sV/2dsb2JhbABYDoJ5vT6Ce4EeF3SCJQEBBTocIxALDgoJJQ8qHgYBiBcBwSOPaQeEMQOYD5IOgmlAOw
Received: from 21.171-179-91.adsl-dyn.isp.belgacom.be (HELO
 kalimero.tijl.coosemans.org) ([91.179.171.21])
 by relay.skynet.be with ESMTP; 16 Nov 2013 13:58:14 +0100
Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org
 [127.0.0.1])
 by kalimero.tijl.coosemans.org (8.14.7/8.14.7) with ESMTP id rAGCwCGH072336;
 Sat, 16 Nov 2013 13:58:13 +0100 (CET)
 (envelope-from tijl@coosemans.org)
Date: Sat, 16 Nov 2013 13:58:11 +0100
From: Tijl Coosemans <tijl@coosemans.org>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>, gerald@FreeBSD.org
Subject: Re: Are clang++ and libc++ compatible?
Message-ID: <20131116135811.23b00fa3@kalimero.tijl.coosemans.org>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2013 12:58:23 -0000

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?