From owner-freebsd-current@FreeBSD.ORG Fri Dec 13 01:12:11 2013 Return-Path: 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 84962DED; Fri, 13 Dec 2013 01:12:11 +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 40EAD1B04; Fri, 13 Dec 2013 01:12:11 +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 rBD1C42f010912; Thu, 12 Dec 2013 17:12:04 -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 rBD1C4Md010911; Thu, 12 Dec 2013 17:12:04 -0800 (PST) (envelope-from sgk) Date: Thu, 12 Dec 2013 17:12:04 -0800 From: Steve Kargl To: Tijl Coosemans Subject: Re: libc++ vs. libstdc++ usage in the ports tree Message-ID: <20131213011204.GA10879@troutmask.apl.washington.edu> References: <20131112201922.GA4330@troutmask.apl.washington.edu> <20131113173143.Horde.a-9M7JQ_vHo3tpDIMsGK6g1@webmail.df.eu> <5283CA3C.3080201@FreeBSD.org> <352D9465-9840-43F0-A3A9-327DC12B0967@FreeBSD.org> <20131114144555.GA22093@troutmask.apl.washington.edu> <52963A90.4000201@janh.de> <20131127204556.2974a3f5@kalimero.tijl.coosemans.org> <20131201150640.12ea18c8@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131201150640.12ea18c8@kalimero.tijl.coosemans.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Maho Nakata , Jan Henrik Sylvester , bapt@FreeBSD.org, FreeBSD Current , stephen@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Fri, 13 Dec 2013 01:12:11 -0000 On Sun, Dec 01, 2013 at 03:06:40PM +0100, Tijl Coosemans wrote: > On Wed, 27 Nov 2013 20:45:56 +0100 Tijl Coosemans wrote: > > On Wed, 27 Nov 2013 19:31:44 +0100 Jan Henrik Sylvester wrote: > >> Trying to migrate to 10, I would like to keep octave. Have you found > >> anything new? Having build the port and all dependencies with standard > >> options, octave is segfaulting for me, too. Anyhow, I can run octave with: > >> > >> env LD_PRELOAD=/usr/lib/libc++.so.1 octave > >> > >> Some very light testing indicates that it is working. Of course, this is > >> not ideal. > >> > >> Maybe this gives a clue how to fix the octave port properly. > > > > I have a preliminary patch for math/octave that I wanted to test on > > redports first, but it is down at the moment so here it is. > > The tests were successful: > https://redports.org/buildarchive/20131201105316-94935/ (octave) > https://redports.org/buildarchive/20131201115701-22333/ (octave-forge-base) > The octave logs also contain the results of running the regression-test > target. The output is the same on all FreeBSD versions. > > The problem is that USE_FORTRAN=yes implies USE_GCC=yes. This means > the C++ code in math/octave is compiled with gcc46/libstdc++ which > does not work if dependencies have been built with clang/libc++. > > The patch copies the USE_FORTRAN=yes logic from Mk/bsd.gcc.mk into a > new file Mk/Uses/fortran.mk. It allows ports to use a Fortran compiler > together with the base system C/C++ compiler. I see the octave port is still broken. After a clean install on my self, removing all installed ports, reverting my local chnages in /usr/pors, and rebuilding all ports, I'm see the original problem. % octave Segmentation fault (core dumped) PLEASE, commit your patch ASAP. -- Steve