This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libg++ as a checkin requirement?
- To: robertl at dgii dot com
- Subject: Re: libg++ as a checkin requirement?
- From: Manfred Hollstein <manfred at s-direktnet dot de>
- Date: Tue, 29 Sep 1998 10:47:46 +0200 (MET DST)
- Cc: egcs at cygnus dot com
- References: <19980928103728.E27775@dgii.com>
- Reply-To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
On Mon, 28 September 1998, 10:37:28, robertl@dgii.com wrote:
> H.J. Lu wrote:
>
> > may be related. It will be nice if people run test on libg++ before
> > they check in changes. I have suggested it many times before. It went
> > nowhere. The result is everyone wastes time on those bugs which can be
> > caught by libg++. Should that be a check-in requirement?
>
> If it is to be a check-in requirement, then we're going to to have dust
> off libg++ and fix some (admittedly minor) portability problems with it.
> It should probably be made part of the CVS tree. We'd need to find the
> dejagnu test stuff that was floating around for a while. In all, we'd
> basically have to accept that the package isn't dead.
All the dejagnu stuff has been incorporated into libg++-2.8.1.2 which
you can find on <ftp://egcs.cygnus.com/pub/egcs/infrastructure>.
>
> I do run libg++ tests once in a while since you suggest we do so. But
> they're so clearly a second-class citizen that it's just too frustrating
> to do it frequently.
>
> RJL
manfred