From owner-freebsd-current@FreeBSD.ORG Wed Nov 14 09:59:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E080958 for ; Wed, 14 Nov 2012 09:59:55 +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 050918FC1B for ; Wed, 14 Nov 2012 09:59:54 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6] (unknown [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 51A705C5A; Wed, 14 Nov 2012 10:59:48 +0100 (CET) Message-ID: <50A36B95.4060901@FreeBSD.org> Date: Wed, 14 Nov 2012 10:59:49 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: AN Subject: Re: -Current built with clang as default + ports References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 09:59:55 -0000 On 2012-11-14 00:51, AN wrote: > Can anyone comment on current built with clang as default compiler and > ports? Are there any major problems, programs that don't run? There are some ports that don't compile, and obviously there will be a few that do compile, but fail to run correctly. Diagnosing the causes is always an interesting venture, you encounter the most diverse problems. See https://wiki.freebsd.org/PortsAndClang for an overview, though some of the instructions are outdated, now clang is the default compiler. Of special interest are the results from the build cluster, where you can get a quick overview of which ports don't build, and how many other ports depend on them. > Specifically, I am > interested in how Gnome and Xorg (Gnome and Xorg built with default > system gcc) work on world built with clang. I don't use Gnome, but Xorg builds just fine with clang, and runs without problems for me. Regarding Gnome, and/or other big frameworks, it is probably best to ask around on the freebsd-ports mailing list, though. > I believe the work around for ports that don't build with clang is to put > USE_GCC=4.7+ in the port makefile, is this correct? Any comments would be > appreciated, thanks in advance. That depends, if the port is easy to fix (borked configure scripts are VERY common), then just fix it. Only if the port is extremely tightly coupled to gcc, or even a very specific gcc version, then use USE_GCC.