This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.0 Release Criteria
- To: ghazi at caip dot rutgers dot edu
- Subject: Re: GCC 3.0 Release Criteria
- From: Geoff Keating <geoffk at cygnus dot com>
- Date: Thu, 27 Apr 2000 14:09:56 -0700
- CC: mark at codesourcery dot com, rth at cygnus dot com, gcc at gcc dot gnu dot org, libc-hacker at sourceware dot cygnus dot com
- References: <200004271445.KAA13474@caip.rutgers.edu>
> Date: Thu, 27 Apr 2000 10:45:42 -0400 (EDT)
> From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
> Cc: gcc@gcc.gnu.org, geoffk@cygnus.com, libc-hacker@sourceware.cygnus.com
> What about dynamic links of binaries? If I develop an app for solaris
> or on linux with a version of gcc newer than the system one, I want to
> link against libgcc.a but dynamically against libc to avoid having to
> distribute libgcc.so. Will we (can we) make this the default behavior?
I believe the whole point of the exercise is that this should not be
allowed, because if libc.so needs a newer version of libgcc then is
linked into the executable then it won't work.
--
- Geoffrey Keating <geoffk@cygnus.com>