From owner-freebsd-gecko@FreeBSD.ORG Mon Jan 28 17:49:19 2013 Return-Path: Delivered-To: gecko@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 90429642; Mon, 28 Jan 2013 17:49:19 +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 4E8A3F16; Mon, 28 Jan 2013 17:49:19 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:84db:bc:f927:3c07] (unknown [IPv6:2001:7b8:3a7:0:84db:bc:f927:3c07]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 83FDF5C43; Mon, 28 Jan 2013 18:49:11 +0100 (CET) Message-ID: <5106BA13.3010803@FreeBSD.org> Date: Mon, 28 Jan 2013 18:49:07 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: Florian Smeets , gecko@FreeBSD.org Subject: Re: Getting www/libxul19 building with clang References: <51040DFC.7090008@FreeBSD.org> <5106B1C5.1080707@smeets.im> In-Reply-To: <5106B1C5.1080707@smeets.im> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Koop Mast , Mark Linimon , Niclas Zeising X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 17:49:19 -0000 On 2013-01-28 18:13, Florian Smeets wrote: > On 26.01.13 18:10, Dimitry Andric wrote: >> I got several reports about www/libxul19 not building with clang. I had >> a look, and gathered a bunch of upstream patches which make it build >> correctly. I am not sure how to run the test suite though, so if >> somebody could please verify it behaves correctly at runtime, that would >> be great. > I'm not sure we should perform any more necromancy on the libuxl19 port. > It has various security vulnerabilities and we would have nuked it a > long time ago if it weren't for all the stuff that still depends on it. Yes, it is only because of the list of dependencies, that I submit this diff. Cleaning up the dependencies one by one can be done incrementally later on, but that will probably take more time than just getting libxul19 building right now. :-) > This has been a long time TODO item on the gecko@ TODO list, but nobody > had the courage to do it, yet... :) > > So I think basically I'm saying I'm ok with fixing it to compile with > clang, but it could get nuked in the not too distant future. I have absolutely no problems with this diff being just a temporary fix. But at least it makes a fair number of additional ports 'accessible' for clang in the mean time. > With the next update we should probably update www/libxul to 17.0.x that > should work with clang out of the box, I believe even the 10.0.x that is > in www/libxul now works with clang. Indeed, some of the patch files in the diff are from upstream authors who are contributors to both Mozilla and the Clang project. IIRC the Clang guys build Mozilla sources (amongst many others) as smoke tests, these days.