From owner-freebsd-ports@FreeBSD.ORG Tue Apr 30 18:08:16 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8FF8A276 for ; Tue, 30 Apr 2013 18:08:16 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 571DA1181 for ; Tue, 30 Apr 2013 18:08:16 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::1113:933:e0bc:5713] (unknown [IPv6:2001:7b8:3a7:0:1113:933:e0bc:5713]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B70805C45; Tue, 30 Apr 2013 20:08:14 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: firefox build broken under clang 3.3 From: Dimitry Andric In-Reply-To: <230B0687-FD64-4BC0-8EB6-D3D6ACD9CC3F@freebsd.org> Date: Tue, 30 Apr 2013 20:07:57 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <53400B33-2A74-4E82-9313-3DE6A7753168@FreeBSD.org> References: <20130419020021.GA16918@test.yahoo.com> <51716917.90101@smeets.im> <517187B9.40106@smeets.im> <230B0687-FD64-4BC0-8EB6-D3D6ACD9CC3F@freebsd.org> To: Brandon Gooch X-Mailer: Apple Mail (2.1503) Cc: kit , freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 18:08:16 -0000 On Apr 30, 2013, at 17:25, Dimitry Andric wrote: ... > In any case, I have just built the latest Firefox from ports, with = clang 3.3, and I see no issues at all. At least with approximately 10 = minutes of browsing, and visiting a varied bunch of sites. I do have it = built with debug info, but without cranking down the optimization level = to -O0 (which is what bsd.port.mk seems to do, unfortunately). >=20 > I will rebuild it again, without any debug info, to see if that makes = any difference. I don't think it will, though... Rebuilt without debug info, worked just fine. Is there a particular = scenario that makes it crash?