From owner-freebsd-ports@FreeBSD.ORG Tue Feb 25 09:57:28 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0191D886 for ; Tue, 25 Feb 2014 09:57:28 +0000 (UTC) Received: from mail.covisp.net (mail.covisp.net [75.148.37.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DA277153D for ; Tue, 25 Feb 2014 09:57:27 +0000 (UTC) Received: from [10.0.0.32] (23-24-150-141-static.hfc.comcastbusiness.net [23.24.150.141]) by mail.covisp.net (Postfix) with ESMTPSA id B239650D3EF for ; Tue, 25 Feb 2014 02:57:20 -0700 (MST) From: LuKreme Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Update gcc? Message-Id: <4291C7F9-A9D8-4DE6-8232-BDA64EDDAF93@kreme.com> Date: Tue, 25 Feb 2014 02:57:18 -0700 To: FreeBSD Ports ML Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2014 09:57:28 -0000 At the risk of starting a kerfuffle, is there any reason to update gcc = on 8.4 or 9.2 from the GPLv2 version 4.2.1 to something more current? (I can think of many reasons *not* to, but they all have to do with = writing code which I am not doing). I know 10.0 moves to clang (which is familiar to me since OS X changed = to clang a while ago because of the GPLv3 issues), but I'm not ready to = move to 10.0 and I know there are still issues with clang and that some = packages still require gcc. --=20 The only reason for walking into the jaws of Death is so's you can steal His gold teeth. --Colour of Magic