This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC 3.0 Release Criteria


> Date: Thu, 27 Apr 2000 17:49:15 -0700
> From: "H . J . Lu" <hjl@lucon.org>

> On Thu, Apr 27, 2000 at 05:42:46PM -0700, Richard Henderson wrote:
> > On Thu, Apr 27, 2000 at 05:33:05PM -0700, Chip Salzenberg wrote:
> > > Multiple versions of libgcc.so will be required on any given system,
> > > because eventually we'll have to make an incompatible change.
> > 
> 
> I am late on this topic. Sorry if it has been resolved.
> 
> If we make libgcc.so, where do we put it? I hope it won't be in
> /prefix/lib/gcc-lib/cpu-vendor-os/version. Otherwise, upgrading
> gcc may break binaries. If we can encode the libgcc ABI into
> it's soname, /prefix/lib/gcc-lib/cpu-vendor-os or
> /prefix/lib/gcc-lib may be candidates.

I would expect that it would go in the same place as libbfd.so and
libstdc++.so, or any other library we built, which depends of course
on whether or not we are cross-compiling or cross-hosting.  That is, I
would expect to see it in /prefix/lib for a native build.

The interaction with multilibs may be more interesting.  Perhaps we
will want to build libgcc-nof.so?
-- 
- Geoffrey Keating <geoffk@cygnus.com>

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]