From owner-freebsd-current@FreeBSD.ORG Fri Aug 30 07:56:38 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 ESMTP id E3B01234; Fri, 30 Aug 2013 07:56:38 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 CBA872EF8; Fri, 30 Aug 2013 07:56:38 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7U7uZVs066226; Fri, 30 Aug 2013 07:56:36 GMT (envelope-from jonathan@FreeBSD.org) Date: Fri, 30 Aug 2013 08:56:35 +0100 From: Jonathan Anderson To: David Chisnall Message-ID: <3C11736737A54D84B80B1D27406F8039@FreeBSD.org> In-Reply-To: References: <20130822200902.GG94127@funkthat.com> <201308291057.43027.jhb@freebsd.org> <8F836479-BC3A-4679-A7AA-3BCDD34AE6C5@FreeBSD.org> <52204746.2070900@freebsd.org> Subject: Re: GCC withdraw X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: FreeBSD Current , Boris Samorodov , toolchain@freebsd.org, "=?utf-8?Q?freebsd-current=40freebsd.org_CURRENT?=" , "Sam Fourman Jr." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 30 Aug 2013 07:56:39 -0000 On Friday, 30 August 2013 at 08:35, David Chisnall wrote: > I would be happy to ship gcc, as long as: > > - It's explicitly marked as deprecated and due for removal at some point in the 10.x timeframe. > - libstdc++ is gone (the amount of pain it's causing ports is phenomenal). 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. I don't see how that's very different from requiring a gcc/g++ package. Jon -- Jonathan Anderson jonathan@FreeBSD.org