From owner-freebsd-current  Fri Jan 28 20:19:49 2000
Delivered-To: freebsd-current@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id C827915230; Fri, 28 Jan 2000 20:19:39 -0800 (PST)
	(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
	by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id XAA06638;
	Fri, 28 Jan 2000 23:19:37 -0500 (EST)
	(envelope-from louie@whizzo.transsys.com)
Message-Id: <200001290419.XAA06638@whizzo.transsys.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: obrien@FreeBSD.ORG
Cc: current@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: new C++ compiler changes 
References: <200001290007.TAA05379@whizzo.transsys.com> 
 <20000128173700.A24289@dragon.nuxi.com>
In-reply-to: Your message of "Fri, 28 Jan 2000 17:37:00 PST."
             <20000128173700.A24289@dragon.nuxi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 28 Jan 2000 23:19:37 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
> > Is it possible to bump the revision of libstdc++ (and perhaps others) so
> > that existing programs can continue to function?
> 
> Nope.  This is -CURRENT and this type of thing happens.  And with a
> RELEASE about to happen, I don't want people continually asking for these
> old libs.
> 

Well, OK, I can deal with this myself.  I'm just concerned about the
folks who will eventually upgrade from 3.4 to 4.0, and have their
C++ programs stop working. 

louie



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