*BSD News Article 72939


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!usenet.ins.cwru.edu!nerd.apk.net!sed.psrw.com!psinntp	!psinntp!psinntp!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!jraynard.demon.co.uk!not-for-mail
From: james@jraynard.demon.co.uk (James Raynard)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: GCC 2.7.2 for FreeBSD ??
Date: 5 Jul 1996 18:18:12 -0000
Organization: A FreeBSD Box
Lines: 34
Message-ID: <4rjm94$2b0@jraynard.demon.co.uk>
References: <4rhnut$23c@wdl1.wdl.loral.com>
NNTP-Posting-Host: localhost
X-NNTP-Posting-Host: jraynard.demon.co.uk

In article <4rhnut$23c@wdl1.wdl.loral.com>,
Richard Toren <rpt@miles.sso.loral.com> wrote:
>I second that request. There has been a great deal of talk and work
>about putting kernel threads into FreeBSD, yet the (not so) current
>compiler can't even compile the (soon to be) ASNI C++ Standard Template
>Library. 

But all the bugs in it (and the necessary workarounds!) are known,
which is rather important if you want to be able to safely re-compile
your operating system with it...

>Hopefully 2.1.5 (dreaming) or 2.2 will include an upgraded compiler.

The problem with gcc is that it doesn't support FreeBSD and has to be
ported from scratch by a core team member; also, it forces you to
update binutils and the libraries at the same time. This has actually
been done for 2.7.2, but only very recently (it hasn't even been
incorporated into -current yet, pending the patches for 2.7.3).

As 2.1.5 is intended to be an incremental bug-fixed improvement on
2.1.0, I would be extremely surprised if the core team were to put a
new version of a critically important component like the C compiler
into it without testing it. In fact, they have already said they're
not going to.

Personally, I think it's very likely that gcc-2.7.3 will be in 2.2; in
the mean time, there's nothing to stop you porting it yourself and
installing it as gcc/g++, or using pgcc from the ports-current
collection.

-- 
James Raynard, Edinburgh, Scotland
james@jraynard.demon.co.uk
http://www.freebsd.org/~jraynard/