[PATCH] lang/gcc -- Fix build on freebsd-current
Steve Kargl
sgk at troutmask.apl.washington.edu
Sat Dec 17 03:35:54 UTC 2011
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 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.
>
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
More information about the freebsd-ports
mailing list