From owner-freebsd-ports@FreeBSD.ORG Tue Jun 22 07:23:52 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E485C106564A for ; Tue, 22 Jun 2010 07:23:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8C68FC16 for ; Tue, 22 Jun 2010 07:23:52 +0000 (UTC) Received: (qmail 30318 invoked by uid 399); 22 Jun 2010 07:23:51 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Jun 2010 07:23:51 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C206505.2060601@FreeBSD.org> Date: Tue, 22 Jun 2010 00:23:49 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100621 Thunderbird/3.0.5 MIME-Version: 1.0 To: bf1783@gmail.com References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: mail/thunderbird3 does not build with gcc 4.5.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 07:23:53 -0000 On 06/21/10 23:25, b. f. wrote: > Doug Barton wrote: >> On to the next victim. :) In my ongoing campaign to build my ports with >> gcc 4.5.1 thunderbird was the next to fall. Full log is at >> http://people.freebsd.org/~dougb/tbird.txt > > Before you embark on this campaign, remember that others have been > experimenting with building ports with later versions of gcc for > months or even years now, and there are suggestions on how to solve > some of the problems that arise in the FreeBSD forums and in the open > PRs. I certainly mean no disrespect to those who've already been working on this problem. I'm really interested in the idea of having a "ports compiler," and I'm trying to do what I can from more of a typical user perspective. If bringing more visibility to the issue helps get more ports fixed, that's a good thing, right? (I'm also trying to fix _my_ ports as I go along as well.) The ultimate goal (in my mind anyway) would be for both src AND ports to be in better shape to be "compiler agnostic" so that newer versions of gcc, clang, or whatever else can be more of a drop-in replacement. I'm not naive enough to think that it will be easy, or even 100% possible. But the more things we _can_ fix the better. > This particular set of problems can probably be solved via > patches similar to those in: > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/142736 > > where some other mozilla ports are discussed. Hopefully the gecko@ team is listening. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/