From owner-freebsd-current@FreeBSD.ORG  Thu Nov 14 14:45:56 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 18365BB5;
 Thu, 14 Nov 2013 14:45:56 +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 CEF852146;
 Thu, 14 Nov 2013 14:45:55 +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 rAEEjtgG022116; 
 Thu, 14 Nov 2013 06:45:55 -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 rAEEjtb5022115;
 Thu, 14 Nov 2013 06:45:55 -0800 (PST) (envelope-from sgk)
Date: Thu, 14 Nov 2013 06:45:55 -0800
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: David Chisnall <theraven@FreeBSD.org>
Subject: Re: libc++ vs. libstdc++ usage in the ports tree
Message-ID: <20131114144555.GA22093@troutmask.apl.washington.edu>
References: <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>
 <20131113173143.Horde.a-9M7JQ_vHo3tpDIMsGK6g1@webmail.df.eu>
 <CAFMmRNxk25AJ3TMuceSG=EmL3qSE9Xhk_wpL5pAD8YvZrA6gkg@mail.gmail.com>
 <5283CA3C.3080201@FreeBSD.org>
 <352D9465-9840-43F0-A3A9-327DC12B0967@FreeBSD.org>
 <B2F7EDA4-DF34-4D5D-B995-5ADA1A9898D8@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B2F7EDA4-DF34-4D5D-B995-5ADA1A9898D8@FreeBSD.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Ryan Stone <rysto32@gmail.com>,
 FreeBSD Current <freebsd-current@FreeBSD.org>,
 Dimitry Andric <dim@FreeBSD.org>, Andriy Gapon <avg@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: Thu, 14 Nov 2013 14:45:56 -0000

On Thu, Nov 14, 2013 at 09:54:52AM +0000, David Chisnall wrote:
> On 13 Nov 2013, at 19:40, Dimitry Andric <dim@freebsd.org> 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

-- 
Steve