From owner-freebsd-current@FreeBSD.ORG Mon May 31 12:22:17 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C91DD1065678 for ; Mon, 31 May 2010 12:22:17 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id A7FD28FC17 for ; Mon, 31 May 2010 12:22:17 +0000 (UTC) Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 642305C85; Mon, 31 May 2010 12:22:11 +0000 (UTC) Date: Mon, 31 May 2010 13:22:05 +0100 From: Bruce Cran To: Astrodog Message-ID: <20100531132205.00000dd6@unknown> In-Reply-To: References: <20100529130240.GA99732@freebsd.org> <20100530135859.GI83316@deviant.kiev.zoral.com.ua> <508DA8CE-749A-46B4-AF0B-392DB08CBBCD@samsco.org> <20100531095617.GR83316@deviant.kiev.zoral.com.ua> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 31 May 2010 12:22:17 -0000 On Mon, 31 May 2010 06:11:32 -0500 Astrodog wrote: > If I understand the build process correctly, it should be possible to > have both compilers in base for some (presumably short) period of > time... then just have which one you use be a configuration option, > which should give LLVM/clang some additional exposure, without the > obvious risks of a complete switch. It should be relatively simply to > have "clang as a compile time option in base" then "clang as default > with gcc as an option" then "clang only", as it proves itself out > building the tree. =46rom previous messages I don't think sparc64 is currently supported by clang very well, if at all, so I think we'll still need gcc in the base system for some time. --=20 Bruce Cran