From owner-freebsd-ports@FreeBSD.ORG Sat Dec 17 03:34:15 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 896A9106566B; Sat, 17 Dec 2011 03:34:15 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id CBCB48FC0A; Sat, 17 Dec 2011 03:34:14 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so7181054wgb.31 for ; Fri, 16 Dec 2011 19:34:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=uUtS3xIujtu/Ml38IsgN46087OU7vJHShr1/XIAIj2s=; b=WDGRBv1/npHDv+dQK1xSkB8IYUjHtMrLa41R02AusMMx5ycALL+u/teHGWCLKPhP48 n1ubko/+TW6vuJUPJ+1tHpr4nfxehropInMroidLzwRkuF6mU7h0F8LO1AiDHFYZWuID BcWRiAXOhk0NO6svvtEH18LVwvIvfg0YB6XXE= MIME-Version: 1.0 Received: by 10.180.14.129 with SMTP id p1mr16318800wic.8.1324092853646; Fri, 16 Dec 2011 19:34:13 -0800 (PST) Received: by 10.180.100.129 with HTTP; Fri, 16 Dec 2011 19:34:13 -0800 (PST) Date: Sat, 17 Dec 2011 03:34:13 +0000 Message-ID: From: "b. f." To: Steve Kargl , Xin LI , Mark Linimon , miwi@FreeBSD.org, gerald@FreeBSD.org, freebsd-ports@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: [PATCH] lang/gcc -- Fix build on freebsd-current 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: Sat, 17 Dec 2011 03:34:15 -0000 > > Actually you can add a dot (.) to these matches, e.g. freebsd[123]* -> > > freebsd[123].*, etc... Have you contacted the maintainer > > (gerald at 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. Fixes have already been implemented upstream, at Gerald's request, and are in lang/gcc46. But these fixes were introduced after the last stable release of gcc 4.6, which corresponds to lang/gcc. When a new version of gcc 4.6 is released, and the port is updated accordingly, it will include the fixes. In the meantime, I think Gerald was waiting for Martin to incorporate the patch to adjust the run-autotools-fixup target in ports/Mk/bsd.port.mk so that the target repairs ports like lang/gcc that use non-default *WRKSRC, by expanding the search in that target to WRKDIR. There hasn't been any further word on that for about a month-and-a-half -- presumably Martin is either busy with other work or is still trying to adjust the patch to fix some other problems. But you can make such a change on your own system. b.