From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 16:59: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 93B991065674 for ; Fri, 4 Jun 2010 16:59:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2505E8FC0A for ; Fri, 4 Jun 2010 16:59:16 +0000 (UTC) Received: (qmail 6309 invoked by uid 399); 4 Jun 2010 16:59:16 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 4 Jun 2010 16:59:16 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C0930E3.3030301@FreeBSD.org> Date: Fri, 04 Jun 2010 09:59:15 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Roman Divacky References: <20100604152605.GA80277@freebsd.org> In-Reply-To: <20100604152605.GA80277@freebsd.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: [INFO]: import of clang/LLVM to happen on June 9th 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: Fri, 04 Jun 2010 16:59:17 -0000 On 06/04/10 08:26, Roman Divacky wrote: > Dear current@ > > On June 9th, we are importing clang/LLVM into FreeBSD HEAD. Excellent news! :) I am in favor of this, and look forward to a day of using a FreeBSD system compiled as much as possible with clang. During the ongoing discussion there were 2 items identified that I was particularly interested in, and I personally would like to see those items resolved before the clang import: 1. Have uname report the compiler (and compiler version?) that the kernel was compiled with. This can likely be done through newvers.sh easily enough. 2. Publish instructions on how to set up a different compiler for ports. I realize that what you're talking about in this announcement is simply importing clang into the build, not using it to build anything yet. However my concern is that if we don't attend to these 2 issues sooner than later that they will get lost in the shuffle. In any case, congratulations on the progress the clang team has made so far, and on this new milestone. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/