Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Feb 1999 13:15:03 -0800
From:      "David O'Brien" <obrien@NUXI.com>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        Warner Losh <imp@harmony.village.org>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, freebsd-current@FreeBSD.ORG
Subject:   Re: gcc
Message-ID:  <19990228131503.A1563@relay.nuxi.com>
In-Reply-To: <199902281707.BAA63212@spinner.netplex.com.au>; from Peter Wemm on Mon, Mar 01, 1999 at 01:07:46AM %2B0800
References:  <199902281648.JAA80190@harmony.village.org> <199902281707.BAA63212@spinner.netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
> The main holdups have been getting the native egcs build to do something
> more sensible with regards to -aout/-elf, and, if things work out, a bit

Work might go a bit faster if the work that has been done already would
be posted somewhere.  Having such an important issue being responsible on
a single over-worked person is not productive.  ***Like Jordan said, we
get NO new install and package utils until EGCS is in the tree.***

Possibly people don't realize how much the public is interested in
improved install and package tools.  At a recent FreeBSD users's group
meeting in San Francisco, Jordan spoke of the new progress on the new
tools.  I'd guess between his speal and the tons of interest and
questions that came up, that the topic was discussed well over an hour.

At a minium the stuff that has already been done should be added to the
port.

ALSO, don't forget that just getting a FreeBSD'ized EGCS is just the
first step.  We will have to test ``build world'' many times and I'm sure
we will have to change base code to compile as we like with EGCS.  The
more people that are allowed to get involved with this the faster things
will go.

In addition, at schools it is getting harder and harder to convince people
to try FreeBSD when we have a broken C++ compiler in the base system.  In
case some aren't aware, C++ is now part of the standard CS curriculum
these days.


> I suspect libg++ is approaching "delete" material.  libstdc++ comes
> with egcs, and a hacked up libg++ is floating around that we can
> probably use, but I wonder if it's time to loose it and keep just
> libstdc++.  

It is time to dump libg++.  Once EGCS is in the tree, I'll make a port of
the libg++ meant for post g++ 2.8 compilers.

-- 
-- David    (obrien@NUXI.com  -or-  obrien@FreeBSD.org)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990228131503.A1563>