From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 17 20:06:54 2012 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 946C1106566C; Mon, 17 Sep 2012 20:06:54 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4C6968FC12; Mon, 17 Sep 2012 20:06:54 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:59a6:c010:f3bf:87fa] (unknown [IPv6:2001:7b8:3a7:0:59a6:c010:f3bf:87fa]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id E9CC55C59; Mon, 17 Sep 2012 22:06:46 +0200 (CEST) Message-ID: <505782D2.2030103@FreeBSD.org> Date: Mon, 17 Sep 2012 22:06:42 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120905 Thunderbird/16.0 MIME-Version: 1.0 To: Brooks Davis References: <20120917191028.GA42648@lor.one-eyed-alien.net> In-Reply-To: <20120917191028.GA42648@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: toolchain@freebsd.org Subject: Re: enabling libc++ by default when building with clang X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2012 20:06:54 -0000 On 2012-09-17 21:10, Brooks Davis wrote: > Now that we have the COMPILER_TYPE variable I'm following up on an idea > by theraven@ that we should enable libc++ by default when we are > building world with a compiler that supports it. The following patch > implements this: > > http://people.freebsd.org/~brooks/patches/libc%2b%2b-default.diff > > One key question is, when do we want to throw this switch? Do we do it > now so people using clang start using it sooner or do we wait until > we've switched the default compiler and things have settled a bit? Well, building libc++ does not mean automatically using it. What is the use case for only building (and installing) libc++, but not linking it to anything? Just so people could build something with it later on? In any case, I have been building libc++ for a long time now, and also did some commits left and right to be able to actually use it for the base system, e.g. all C++ programs in my installations are already linked to libc++ (dynamically or statically). I have seen no problems at all, and I am even working on a WITHOUT_LIBSTDCPLUSPLUS option. :) I think the end goal should be to enable building and using libc++ with one switch. And sooner or later, to make that the default. Then FreeBSD will finally be able to use C++0x and C++11 features natively.