[PATCH] lang/gcc -- Fix build on freebsd-current

b. f. bf1783 at googlemail.com
Sat Dec 17 03:34:15 UTC 2011

> > 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


More information about the freebsd-ports mailing list