Subject: Re: our libstdc++.so.3 vs GCC 3.0
To: Todd Vierling <tv@wasabisystems.com>
From: Nick Hudson <nick@nthcliff.demon.co.uk>
List: tech-toolchain
Date: 08/01/2001 17:16:39
Todd Vierling wrote:
> 
> On Thu, 2 Aug 2001, matthew green wrote:
> 
> : so, i think we're screwed.
> :
> : GCC 3.0 defaults to building a shared libstdc++ on many platforms, and the
> : version number of this shlib is 3.  we unfortunately have called our
> : egcs 1.1.2-based libstdc++ .so.3, so this conflicts... it's quite annoying,
> : as programs linked against $gcc-prefix/lib/libstdc++.so runtime link with
> : /usr/lib/libstdc++.so.3, unless explicit ld -rpath/LD_LIBRARY_PATH are used.

[...]
 
> There may be ways around this, not the least of which is to twiddle the
> -soname in the libstdc++ being used for our in-tree 2.95 (since the in-tree
> 2.95 build isn't part of any official NetBSD release yet).  I'll get back to
> you.

How does this work with a.out? Or is the idea to kill a.out before the
release that contains 2.95?

Nick