GCC 3.4 import and ports system

Guido Falsi mad at madpilot.net
Mon Aug 16 07:30:22 PDT 2004


On Mon, Aug 16, 2004 at 02:04:58PM +0200, Oliver Eikemeier wrote:
> >
> >I'd like to know why the ports system is not still differentiating
> >between freebsd versions before and after the gcc 3.4 import...in fact
> >it looks strnge to me there has been no bump in OSVERSION (and
> >__FreeBSD_version) to mark this change. It was done for most(all?) 
> >previous
> >compiler imports...
> The OSVERSION marking the gcc 3.4.2 import is 502126:
>   <http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-
> handbook/freebsd-versions.html>

Oops...Sorry. It got past my eyes. Thank you for pointing it to me.

> >My problem is with the netpanzer port I'm maintaining. it fails with gcc
> >3.4, I'm trying to force it to use gcc 3.3, but the ports system does
> >not ntice that gcc 3.4 is in the system(logic in bsd.port.mk will use
> >the system gcc when 3.3 is requested on anything above OSVERSION
> >501103).
> >I could mark the port broken but am not sure how to correctly recognize
> >-current after gcc 3.4 import.
> 
> Ehm - how about patching it so that it compiles with gcc 3.3 and 3.4? 
> And submitting this patches upstream, so that it will be fixed in the 
> next vendor version.

I'd really like that, but looking at the software sources it really goes
beyond my C++ language knowledge. I'm trying to figure it out but it
will anyway take time. I'd like to find some kind of solution to the
problem before the ports code freeze for 5.3.

I've anyway reported the problem to the developers. I hope they will
take steps to fix the incompatibility.

-- 
Guido Falsi <mad at madpilot.net>


More information about the freebsd-ports mailing list