Date: Tue, 28 Jun 2005 11:39:46 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: David O'Brien <obrien@freebsd.org> Cc: kan@freebsd.org, stable@freebsd.org Subject: Re: libstdc++ version bump. Message-ID: <20050628183946.GL40423@elvis.mu.org> In-Reply-To: <20050628182701.GA92486@dragon.NUXI.org> References: <20050628154627.GJ40423@elvis.mu.org> <20050628182701.GA92486@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* David O'Brien <obrien@freebsd.org> [050628 11:27] wrote: > On Tue, Jun 28, 2005 at 08:46:27AM -0700, 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? > > Because 5.2.1 was 5-CURRENT. Not until 5.3 did we make any ABI stability > cares or guarantees. It was a conscientious decision the release > management team made. I'm sure one could have built a 5.2.1 kernel > module (.ko) that is broken on 5.3-RELEASE and 5-STABLE. The difference between kernel compat and userland binary compat... [godwin's law] How very upsetting. Thanks for your help on chat though. Hopefully linking static against libstdc++ on the 5.2.1 machine will fix things. -- - Alfred Perlstein - email: bright@mu.org cell: 408-480-4684
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050628183946.GL40423>