From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 06:04:55 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A44D106564A for ; Wed, 12 Sep 2012 06:04:55 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 73E7A8FC0C for ; Wed, 12 Sep 2012 06:04:55 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 3886F5625E; Wed, 12 Sep 2012 01:04:20 -0500 (CDT) Date: Wed, 12 Sep 2012 01:04:20 -0500 From: Mark Linimon To: Andreas Nilsson Message-ID: <20120912060420.GE31029@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Mailing List Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 06:04:55 -0000 On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote: > Is there a specif PR to use for ports that fails with clang and does > not specify to use gcc ( > devel/cdecl and deskutils/calibre so were > the culprits so far) There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say "broken on clang" doesn't really help us all that much. mcl