This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Got NEWS?
- To: law at cygnus dot com
- Subject: Re: Got NEWS?
- From: hjl at lucon dot org (H.J. Lu)
- Date: Mon, 27 Jul 1998 16:26:15 -0700 (PDT)
- Cc: jason at cygnus dot com, egcs at cygnus dot com
>
>
> In message <m0z0sT0-00038pC@ocean.lucon.org>you write:
> > >
> > > Here's what we have in the C++ NEWS file currently; anything I've missed
> > > that should be mentioned for 1.1?
> > >
> >
> > I'd like to see my library interface in 1.1. Otherwise, it may be
> > a disaster for Linux where libstdc++ is usd by the system. It is very
> > likely that
> >
> > # configure --prefix=/usr
> I suspect most folks do not do this. And I certainly do not recommend
> doing this since it overwrites files in the "system area".
That is not the point. Suppose a Linux user installed egcs 1.0.3 under
/usr/local and compiled/installed a bunch of C++ progams which use
shared libstdc++ in /usr/local/lib. Now when he/she upgrades to egcs
1.1, his/her existing C++ binaries may not run at all. My library
interface patch addresses this problem. As I mentioned before, a C++
library ABI is determined by libc ABI/API, libstdc++ ABI/API and C++
compiler interface. The current scheme for shared library name is
broken, especially on Linux, where we have 3 different C libraries with
3 different ABIs, libc 5, glibc 2.0 and glibc 2.1. We should address
it in egcs 1.1.
--
H.J. Lu (hjl@gnu.org)