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]
Other format:	[Raw text]

Re: gcc 3.3

From: "H. J. Lu" <hjl at lucon dot org>
To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
Cc: chrishickman at free-market dot net, gcc at gnu dot org
Date: Tue, 30 Jul 2002 19:58:59 -0700
Subject: Re: gcc 3.3
References: <3D46DC60.9060004@stonepool.com> <20020731074109.A29189@hg.cs.mu.oz.au> <20020730162145.B8991@lucon.org> <20020731122857.A29806@hg.cs.mu.oz.au>

On Wed, Jul 31, 2002 at 12:28:57PM +1000, Fergus Henderson wrote:
> > 
> > Why will the new libfoo.so break bar if it is binary compatible with
> > the old libfoo.so?
> 
> It's not guaranteed to be binary compatible with the old libfoo.so.
> The source for libfoo has not changed.
> However, libfoo may have dependencies on libstdc++
> that mean that libfoo's ABI changes if/when libstdc++'s ABI changes
> and libfoo is recompiled with the new libstdc++.
> 

Is this any different from glibc? That is not a new problem. You just
have to deal with it. Sometimes, it may not be an easy thing to do. 


H.J.

References:
- gcc 3.3
  - From: Chris M. Hickman
- Re: gcc 3.3
  - From: Fergus Henderson
- Re: gcc 3.3
  - From: H. J. Lu
- Re: gcc 3.3
  - From: Fergus Henderson

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