From owner-freebsd-current@FreeBSD.ORG Tue Mar 4 17:48:29 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5457AB10 for ; Tue, 4 Mar 2014 17:48:29 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2E70D1A1 for ; Tue, 4 Mar 2014 17:48:29 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.8/8.14.8) with ESMTP id s24HMaIl087622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Mar 2014 09:22:36 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.8/8.14.8/Submit) id s24HMYPg087621; Tue, 4 Mar 2014 09:22:34 -0800 (PST) (envelope-from sgk) Date: Tue, 4 Mar 2014 09:22:34 -0800 From: Steve Kargl To: Thomas Mueller Subject: Re: Status of llvm/clang 3.4? Message-ID: <20140304172234.GA87591@troutmask.apl.washington.edu> References: <634745.72215.bm@smtp120.sbc.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <634745.72215.bm@smtp120.sbc.mail.bf1.yahoo.com> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 04 Mar 2014 17:48:29 -0000 On Tue, Mar 04, 2014 at 12:17:18PM +0000, Thomas Mueller wrote: > What is the current status of clang, regarding known bugs, on FreeBSD-current? > > There were reports of www/firefox failing to build because of bug in llvm. Still broken of i386. Given the google results for "llvm ud2" it is likely that clang will never be fixed. > Can I currently build ports normally on FreeBSD-current amd64 and i386, > or do I need to wait? I can build all ports that I use except firefox. Chrome seems to work. -- Steve