From owner-freebsd-current@FreeBSD.ORG Wed Nov 27 18:31:54 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 4EE2049A; Wed, 27 Nov 2013 18:31:54 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9AD72039; Wed, 27 Nov 2013 18:31:52 +0000 (UTC) Received: from pc1111.math.uni-hamburg.de (pc1111.math.uni-hamburg.de [134.100.220.119]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MYaEY-1W7CfU0GDC-00VQK1; Wed, 27 Nov 2013 19:31:50 +0100 Message-ID: <52963A90.4000201@janh.de> Date: Wed, 27 Nov 2013 19:31:44 +0100 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Steve Kargl Subject: Re: Re: libc++ vs. libstdc++ usage in the ports tree References: <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> <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> In-Reply-To: <20131114144555.GA22093@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:JdZ5Eu3sfmoxrw3NNX8uc0gyPbZwIFb3cZVxGYwtmt+ t3PI8a3ti5nM6bVpSFfxyrTXzOOUw2FV76iuZ7DKun6N1X3nPd g2FT26Z7NiVzXv7kAAB08zlfOC0lcxnX+re14Kipx/4qsUHwuQ JPLTWrNMY5Ulq4xlfBfGcZ+eYYYq4BvMGMiWZu56Uxg+MuEOw1 7kjBf+XSDmh/vQ9EzgHZsXyC3ml1mJvifH748O514IvqYfR4R3 BYJGzP52BGKJWCOYq4qhtpCZoXpQjpVtd/CHJTj/pS8T2bssqu NQCzL2S97JAw++Qwq/MsiAv8qOc3/SbcCrP8Ioh1Q/Mn3dDlOA 7m5mK5kg+JW3eU1niknw= X-Mailman-Approved-At: Wed, 27 Nov 2013 18:49:06 +0000 Cc: Dimitry Andric , David Chisnall , Andriy Gapon , Maho Nakata , FreeBSD Current , Ryan Stone 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: Wed, 27 Nov 2013 18:31:54 -0000 On 11/14/2013 15:45, Steve Kargl wrote: > On Thu, Nov 14, 2013 at 09:54:52AM +0000, David Chisnall wrote: >> On 13 Nov 2013, at 19:40, Dimitry Andric wrote: >> >>> On the other hand, different C++ standard libraries simply cannot be >>> mixed. The internal implementations are usually completely different. >>> This is not really news at all, certainly not to the ports people. :-) >> >> That said, it should still be possible to mix them in different >> libraries. The constraint from the wiki still applies: if you >> don't use STL types at library boundaries, then it should still >> work. If you do, then the libc++ and libstdc++ symbols will be >> mangled differently and so you will get link-time errors. >> >> In theory, if it links it should run... >> > > 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 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. Cheers, Jan Henrik