From owner-freebsd-stable@FreeBSD.ORG Tue Jun 28 16:47:05 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 937B316A43B; Tue, 28 Jun 2005 16:47:04 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C42443D53; Tue, 28 Jun 2005 16:47:04 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id F27C25C9F2; Tue, 28 Jun 2005 09:47:03 -0700 (PDT) Date: Tue, 28 Jun 2005 09:47:03 -0700 From: Alfred Perlstein To: Scot Hetzel Message-ID: <20050628164703.GK40423@elvis.mu.org> References: <20050628154627.GJ40423@elvis.mu.org> <790a9fff05062809211c27a435@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <790a9fff05062809211c27a435@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: kan@freebsd.org, stable@freebsd.org, obrien@freebsd.org Subject: Re: libstdc++ version bump. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2005 16:47:05 -0000 No, it's not that. It's just that when we decided to upgrade gcc/g++ in the 5.2.1 era someone didn't bump the library version for libstdc++. It would have been a two second change, but instead it appears that it was decided that early adopters REALLY needed to be put in their place for being stupid enough... to be early adopters. So the library wasn't bumped and people are stuck having to do source upgrades from 5.2.1->5.3+ instead of the right thing. There's not much choice at this point because the decision was made so long ago, if we did a bump now, we'd basically lose a lot of package compatibility between 5.3+ and 6.x. (Oh dear, losing package compat between current (where things are supposed to break) and 5.x... ) Although the relative worth of that versus actually doing the right thing and giving people stuck with 5.2.1 and prior room to breath is something that is very debatable. -Alfred * Scot Hetzel [050628 09:22] wrote: > This note in the 5-CURRENT UPDATING file (when -CURRENT was 5.x), > indicates you'll need to rebuild all 5.x executables made after this > change (20041001 entry). > > http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.diff?r1=1.366&r2=1.367&f=h > > /lib/libm.so.2 -> libm.so.3 > /lib/libreadline.so.4 -> libreadline.so.5 > /usr/lib/libhistory.so.4 -> libhistory.so.5 > /usr/lib/libopie.so.2 -> libopie.so.3 > /usr/lib/libpcap.so.2 -> libpcap.so.3 > > Are you sure that the problem is with libstdc++ and not the above libraries? > > Was there any changes to libstdc++ between 5.4 & 5.3? > > Scot > > On 6/28/05, Alfred Perlstein wrote: > > I just got bitten by an upgrade from 5.2.1 to 5.4 where my apps > > linked with c++ stopped working. The solution I had to do was to > > copy an old 5.2.1 libstdc++ over my 5.4 one. My question is, why > > wasn't the library version bumped for this incompatible change? > > > > Can we bump it? > > > > How can we bump it? > > > > Even if it doesn't solve 100% of people's problems, it appears > > to solve some of mine. So can we do it? > > > > thank you, > > -- > > - Alfred Perlstein > > - email: bright@mu.org cell: 408-480-4684 > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. -- - Alfred Perlstein - email: bright@mu.org cell: 408-480-4684