From owner-freebsd-current@FreeBSD.ORG Thu Nov 28 04:25:46 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 3AC71FA4; Thu, 28 Nov 2013 04:25:46 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F13341254; Thu, 28 Nov 2013 04:25:45 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id y13so11325546pdi.33 for ; Wed, 27 Nov 2013 20:25:45 -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=92MOSzoj4eNje/xD66yogAjhv/86Od9MVRFnvgvri5c=; b=tHNDhg+tDp+0ReHTWP32gIiJUVCp4tzn8vC8KiVQZMdcXtg7570EIpvWqY9esHqCSa Ee9NG4NNgjg06pB0brzjAW05h+lFAWzDTwaq//IncOUYtiBo5I+JhA1pJPD+np/5C/Qs e49e0ZGH2Jg5kSnB9hYwDRxmYJ+rmVA0lgA7PTBKRHFn3lDgtH/mteNgFLYhk+niP/7C dJwb1k8Jzlg4jEhz4yItAAszYyxJsOsnRYKllr93xNr5o2dsRQOnOESkgPu2WCfDyRBG KaBOtwKFXfhSMHyXfcwYTZS0znf4A29Vu8xslMn81RI0JWu2gKnygv+A6HAsx3oXvuCZ ma2g== X-Received: by 10.68.233.135 with SMTP id tw7mr8722491pbc.112.1385612745566; Wed, 27 Nov 2013 20:25:45 -0800 (PST) Received: from localhost (rikad42.riken.jp. [134.160.214.42]) by mx.google.com with ESMTPSA id ka3sm91793318pbc.32.2013.11.27.20.25.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Nov 2013 20:25:44 -0800 (PST) Date: Thu, 28 Nov 2013 13:25:40 +0900 (JST) Message-Id: <20131128.132540.2082341321179147888.maho.nakata@gmail.com> To: sgk@troutmask.apl.washington.edu Subject: Re: libc++ vs. libstdc++ usage in the ports tree From: Nakata Maho In-Reply-To: <20131127184302.GA15006@troutmask.apl.washington.edu> References: <20131114144555.GA22093@troutmask.apl.washington.edu> <52963A90.4000201@janh.de> <20131127184302.GA15006@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: Thu, 28 Nov 2013 05:34:54 +0000 Cc: me@janh.de, dim@FreeBSD.org, theraven@FreeBSD.org, avg@FreeBSD.org, freebsd-current@FreeBSD.org, rysto32@gmail.com 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: Thu, 28 Nov 2013 04:25:46 -0000 Hmm thanks for discussion. I'll install and test FBSD 10 in this weekend. thanks Nakata Maho From: Steve Kargl Subject: Re: Re: libc++ vs. libstdc++ usage in the ports tree Date: Wed, 27 Nov 2013 10:43:02 -0800 > On Wed, Nov 27, 2013 at 07:31:44PM +0100, Jan Henrik Sylvester wrote: >> On 11/14/2013 15:45, Steve Kargl wrote: >> > >> > And in practice, it is broken. >> > >> > http://lists.freebsd.org/pipermail/freebsd-current/2013-November/046565.html >> > >> > QED >> >> 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 >> > > Unfortunately, you need to add "USE_GCC=any" to math/octave/Makefile, > and rebuild it. You theni need to run "ldd -a | more" and search for > shared libraries that are linked against both libc++ and libstdc++. > Then, add "USE_GCC=any" to those ports' Makefile and recompile. > I recall at least 4 that needed to be rebuilt, but only remember > fltk and libgraphite2. > > -- > Steve >