From owner-freebsd-current@FreeBSD.ORG Tue Mar 4 14:04:58 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D02F5704 for ; Tue, 4 Mar 2014 14:04:58 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D5F99C0 for ; Tue, 4 Mar 2014 14:04:58 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MIzGn-1WMkhv3Re5-002bTn; Tue, 04 Mar 2014 15:04:50 +0100 Message-ID: <5315DD83.2000806@gmx.net> Date: Tue, 04 Mar 2014 15:04:51 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-current@freebsd.org Subject: Re: Status of llvm/clang 3.4? References: <634745.72215.bm@smtp120.sbc.mail.bf1.yahoo.com> In-Reply-To: <634745.72215.bm@smtp120.sbc.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:vqaaa0ARxyLRKIhMMpHci6Jzd0JmIMH/ea0Gh7AyY5gFyR5ehO2 /u0x8sXbwHcMXMe9LGURj8onzw4vSO1HV4F7z0zEi0k+fGQ50UIuYhBgYyzwvLyT04cJH5m uJ9l4FNIR1y8Jz0mbtTTakozq2zzCYyU3LGQDxObgY88h5rfy7y7PMFjVt9GIS54k0aVe0e D4yeb7cVxqZwIXQk3Qt1Q== 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 14:04:58 -0000 On 04.03.2014 13:17, 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. > > Can I currently build ports normally on FreeBSD-current amd64 and i386, or do I need to wait? > > Or update system and build ports on my FreeBSD 10-stable amd64 and i386 installations while I wait for bug fix? Recently I had problems with building py-sqlite3 while building firefox, something like unknown clang arguments ('-R' or something) are errors now. Yesterday I built (via ssh) fresh kernel/world/ports and everything worked fine (the build). Today I will try the binaries with direct access to the machine. Cheers Michael