From owner-freebsd-ports@FreeBSD.ORG Sat Dec 17 03:35:54 2011 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 C80DD106566B for ; Sat, 17 Dec 2011 03:35:54 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8D19A8FC15 for ; Sat, 17 Dec 2011 03:35:54 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id pBH3Zsx2000512; Fri, 16 Dec 2011 19:35:54 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id pBH3Zsip000511; Fri, 16 Dec 2011 19:35:54 -0800 (PST) (envelope-from sgk) Date: Fri, 16 Dec 2011 19:35:54 -0800 From: Steve Kargl To: Mark Linimon Message-ID: <20111217033554.GB456@troutmask.apl.washington.edu> References: <20111217002404.GA70926@troutmask.apl.washington.edu> <20111217031506.GA6234@lonesome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111217031506.GA6234@lonesome.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-ports@freebsd.org Subject: Re: [PATCH] lang/gcc -- Fix build on freebsd-current 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: Sat, 17 Dec 2011 03:35:54 -0000 On Fri, Dec 16, 2011 at 09:15:06PM -0600, Mark Linimon wrote: > On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: > > Actually you can add a dot (.) to these matches, e.g. freebsd[123]* -> > > freebsd[123].*, etc... Have you contacted the maintainer > > (gerald@FreeBSD.org) by the way? > > My guess? We should rip out the [123] and [23] strings entirely. If > anyone is running ports on FreeBSD 1, they have more problems than they > can count right now. > > I can personally guarantee that ports don't work on 4.x (I ripped out > the compat code several years ago that dealt with gross old make(1) > bugs, etc.) and I think that means not 3.x either. In any case, the > official claim is that the Ports Collection only supports 789 as first- > class citizens right now, not anything older. > gerald@ has indicated that he'll do something with the official GCC way to deal with 1. versus 10. This patch is a stop gap for others, who like me, will run into a broken lang/gcc while we wait for a better solution. -- Steve