This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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

To: Richard Henderson <rth at cygnus dot com>
Subject: Re: GCC 3.0 Release Criteria
From: "H . J . Lu" <hjl at lucon dot org>
Date: Thu, 27 Apr 2000 17:49:15 -0700
Cc: Chip Salzenberg <chip at valinux dot com>,"Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, mark at codesourcery dot com,gcc at gcc dot gnu dot org, geoffk at cygnus dot com, libc-hacker at sourceware dot cygnus dot com
References: <200004271445.KAA13474@caip.rutgers.edu> <20000427095256.C11838@cygnus.com> <20000427173305.J570@perlsupport.com> <20000427174246.C12403@cygnus.com>

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.

H.J.

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