From owner-freebsd-ports@FreeBSD.ORG Tue Jun 22 11:39:53 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 839081065686 for ; Tue, 22 Jun 2010 11:39:53 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1B1478FC1A for ; Tue, 22 Jun 2010 11:39:52 +0000 (UTC) Received: by wwe15 with SMTP id 15so1118158wwe.13 for ; Tue, 22 Jun 2010 04:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=Z0wpmK7a/aCXfBuA7Mt1mFsUzi0W0CNtNJvG6eIWs4c=; b=kNRDnsV63/vEqr130GAKhkdu4epM44S82ODnnUSncEbqAZU/DKeVRvIGk2DTAk1la7 cjsUywv0Ss00sq0nHfpD3H8lq0QI0xDDA268wLfo76YvhdOeUELYWSY/GL7vL87b/suX iEGtE/7rS1aImwTys7CA9CikTLZu35i4ub8LI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=uGJ1VA6qBY1lva53RVqpEu5TA/ROP0lhrNlRkmyPCAylQfx6PPY4bxToUa2x0/lWTd lqiZVPUoAGNUiEbosELQ2kRepT9K0LBznRASYPJ/Wee4+LuYRx99m71kmZkqa4Nl6pCd 4jKEm5Mk7tAlJ8ukW92BODb4HBhOJFJImTnyA= MIME-Version: 1.0 Received: by 10.216.85.143 with SMTP id u15mr1184150wee.113.1277206788612; Tue, 22 Jun 2010 04:39:48 -0700 (PDT) Received: by 10.216.168.1 with HTTP; Tue, 22 Jun 2010 04:39:48 -0700 (PDT) In-Reply-To: <4C206505.2060601@FreeBSD.org> References: <4C206505.2060601@FreeBSD.org> Date: Tue, 22 Jun 2010 11:39:48 +0000 Message-ID: From: "b. f." To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 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 Reply-To: bf1783@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 11:39:53 -0000 On 6/22/10, Doug Barton wrote: > 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. > Yes, of course. I didn't mean to suggest that I thought you were being disrespectful, but only to let you know that you may solve some of these problems more quickly by skimming through the open PRs, mailing lists archives, and forum listings first. Also, because many GNU/Linux distros, NetBSD, and DragonflyBSD have switched to later versions of gcc and/or binutils than we have in our base system, other packaging systems (especially Red Hat Fedora's Rawhide packages, Gentoo Portage, and NetBSD pkgsrc) may have relevant patches, especially for older software. Also, http://gcc.gnu.org/gcc-4.3/porting_to.html http://gcc.gnu.org/gcc-4.4/porting_to.html http://gcc.gnu.org/gcc-4.3/changes.html http://gcc.gnu.org/gcc-4.4/changes.html http://gcc.gnu.org/gcc-4.5/changes.html http://gcc.gnu.org/gcc-4.6/changes.html provide useful hints for some problems related to re-factoring of compiler headers, and changes in compiler defaults (those for earlier versions of gcc than the one you have mentioned may contain information that is also applicable to 4.5 and 4.6). I think it would be good if someone posted tinderbox results for exp-runs of ports built with the latest stable branch of gcc, and with clang, to show which ports need to be patched. Perhaps that fellow who has a GSoC project to make it possible to use clang with the Ports system may be willing to do this, at least for clang. I can tell you right now from my own experiences that the ports infrastructure and many individual ports do not respect the necessary compiler and toolchain-related variables. b.