From owner-freebsd-current@FreeBSD.ORG  Fri Aug 30 07:59:15 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: 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 ESMTP id 2DF6D3C8;
 Fri, 30 Aug 2013 07:59:15 +0000 (UTC)
 (envelope-from theraven@FreeBSD.org)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id EB73B2F26;
 Fri, 30 Aug 2013 07:59:14 +0000 (UTC)
Received: from [192.168.0.2]
 (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236])
 (authenticated bits=0)
 by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7U7xBlG007438
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Fri, 30 Aug 2013 07:59:13 GMT (envelope-from theraven@FreeBSD.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: GCC withdraw
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <3C11736737A54D84B80B1D27406F8039@FreeBSD.org>
Date: Fri, 30 Aug 2013 08:59:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <53AB1421-BC0C-4F29-B799-721553B3B1DA@FreeBSD.org>
References: <20130822200902.GG94127@funkthat.com>
 <CAOFF+Z3vbOgMO7T-BKZnhKte6=rFoGcdYcft5kpAgNH2my1JKg@mail.gmail.com>
 <DC41B4BD-159A-408B-804A-0230F3E0E52B@FreeBSD.org>
 <201308291057.43027.jhb@freebsd.org>
 <8F836479-BC3A-4679-A7AA-3BCDD34AE6C5@FreeBSD.org>
 <52204746.2070900@freebsd.org>
 <ADADF693-B140-4C87-B464-9F139B31E7B5@FreeBSD.org>
 <3C11736737A54D84B80B1D27406F8039@FreeBSD.org>
To: Jonathan Anderson <jonathan@FreeBSD.org>
X-Mailer: Apple Mail (2.1508)
Cc: "Sam Fourman Jr." <sfourman@gmail.com>, toolchain@FreeBSD.org,
 "freebsd-current@freebsd.org CURRENT" <freebsd-current@FreeBSD.org>,
 Boris Samorodov <bsam@passap.ru>, FreeBSD Current <current@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 30 Aug 2013 07:59:15 -0000

On 30 Aug 2013, at 08:56, Jonathan Anderson <jonathan@freebsd.org> =
wrote:

> Wouldn't this mean that we can't build base using the shipped-in-base =
g++? If we have C++ in base, we don't ship libstdc++ and g++ can't work =
with libc++, then people wanting to compile the base system with gcc/g++ =
will have to install a libstdc++ package.

People wanting to build base with g++ will still have to explicitly =
enable the build of libstdc++, yes.  That's only really an issue for =
10.0 though, because in 10.1 we won't be able to build clang (or lldb) =
with either g++ from base or our libstdc++ from base, as both use C++11 =
features.

David