From owner-freebsd-current@FreeBSD.ORG Fri Dec 13 11:37:30 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 1964FE00; Fri, 13 Dec 2013 11:37:30 +0000 (UTC) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE9971F51; Fri, 13 Dec 2013 11:37:29 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id p10so2349089pdj.40 for ; Fri, 13 Dec 2013 03:37:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=vDFPk4eJMTmkg29wYL0eMnECVaN/lpr7l5hwICRoi20=; b=QaqALXI24KsTF78x8RlqctorbxLT9b29Jank7k2iomLe/2UFcSm7WtUki1VaTKCnco LFNi5Ghl6DwvdKzazzHq6bL6U0NFKJqKA+Ap9iclrhT1yWuBegx9WTTBFwhGbZCQ7anO O8eo3+Kc+uHv6Ef7Q6tCWMi5crEw0Yi0+Yr18l0pc7+jZHRCyA2zPEy9jzDb2rpZ8xyb Neu/ctuO7yjmQS0ixINjyTdLyaJD4BIIoTmIfDrC42HLG4G79D4wcvz3tXhC2pwX6pWu hyxJxQSPfh29n8OMJf3RpT4orsAgtqvpyRYBlN8mUF015lVORtul0rsTQbkRvhBcNDya Py7Q== X-Received: by 10.66.251.98 with SMTP id zj2mr2600945pac.45.1386934649439; Fri, 13 Dec 2013 03:37:29 -0800 (PST) Received: from localhost (rikad42.riken.jp. [134.160.214.42]) by mx.google.com with ESMTPSA id sg1sm4248529pbb.16.2013.12.13.03.37.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Dec 2013 03:37:27 -0800 (PST) Date: Fri, 13 Dec 2013 20:37:15 +0900 (JST) Message-Id: <20131213.203715.134153284229331604.maho.nakata@gmail.com> To: stephen@FreeBSD.org Subject: Re: libc++ vs. libstdc++ usage in the ports tree From: Nakata Maho In-Reply-To: <20131213011204.GA10879@troutmask.apl.washington.edu> References: <20131127204556.2974a3f5@kalimero.tijl.coosemans.org> <20131201150640.12ea18c8@kalimero.tijl.coosemans.org> <20131213011204.GA10879@troutmask.apl.washington.edu> X-Mailer: Mew version 6.3 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 13 Dec 2013 12:29:18 +0000 Cc: me@janh.de, tijl@FreeBSD.org, freebsd-current@FreeBSD.org, bapt@FreeBSD.org, sgk@troutmask.apl.washington.edu 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 11:37:30 -0000 Hi all Does anybody please commit the patch? My FreeBSD machine is down due to power outage for next week. Also I'll be very busy in the next week. Best, Nakata Maho From: Steve Kargl Subject: Re: libc++ vs. libstdc++ usage in the ports tree Date: Thu, 12 Dec 2013 17:12:04 -0800 > 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 >