From owner-svn-ports-head@FreeBSD.ORG Sun Nov 3 14:34:46 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8225858D; Sun, 3 Nov 2013 14:34:46 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 562B22197; Sun, 3 Nov 2013 14:34:45 +0000 (UTC) Received: from [192.168.0.22] (unknown [130.255.26.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 70CB543600; Sun, 3 Nov 2013 08:34:15 -0600 (CST) Message-ID: <52765ED2.8080205@marino.st> Date: Sun, 03 Nov 2013 15:33:54 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Gerald Pfeifer Subject: Re: svn commit: r332557 - head/lang/gcc References: <201311022320.rA2NKEcg089316@svn.freebsd.org> <20131103110034.GA80884@graf.pompo.net> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Thierry Thomas , svn-ports-all@freebsd.org, Gerald Pfeifer , ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: marino@freebsd.org List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Nov 2013 14:34:46 -0000 On 11/3/2013 14:59, Gerald Pfeifer wrote: > On Sun, 3 Nov 2013, Thierry Thomas wrote: >>> Update to GCC 4.6.4 which, among others, addresses document building >>> with new versions of texinfo. [1] >> Do we still need lang/gcc and lang/gcc46? > > Yes, since lang/gcc is the canonical version that should be used > (and is pulled in by USE_GCC=yes, for example). At that point > lang/gcc46 will be the final release of GCC 4.6, lang/gcc47 > will track GCC 4.7 and lang/gcc will track GCC 4.7 releases. > > lang/gcc should have been upgraded to GCC 4.7 already (and hopefully > will in the not too far future, there are just still a number of broken > ports -- see below for those not Python-related). > > Gerald > > > Done. List of failures and logs: > > http://package20.nyi.freebsd.org/bulk/91amd64-default-gccupdate/2013-10-22_01h02m27s/ > >> + {"origin"=>"biology/plink", "pkgname"=>"plink-1.07", "phase"=>"build", "errortype"=>"cluster"} > > C++ error. [snipped] DragonFly has moved to use gcc 4.7 already and may already have the fixes. For example, plink builds on gcc 4.7 in DragonFly right now. So for sure some of these can be transferred to avoid rework. However, food for thought: Moving to gcc47 and exposing the resulting package could have the benefit of others providing the fixes. I can tess you from experience these last 3 weeks that c++ breakage is very slow to fix so people will be waiting a long time. I've been doing this for all the 4.4 to 4.7 fallout I've seen. Luckily much of those fixes I've put directly in ports. John