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: c++ link incompatibility between 3.4.0 and 3.4.1-20040625

From: Daniel Jacobowitz <drow at false dot org>
To: Benjamin Kosnik <bkoz at redhat dot com>
Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, nick at ilm dot com
Date: Thu, 1 Jul 2004 00:47:35 -0400
Subject: Re: c++ link incompatibility between 3.4.0 and 3.4.1-20040625
References: <20040701031930.GO24996@ewok.lucasdigital.com> <40E38951.10409@codesourcery.com> <20040630232002.2007a8a5.bkoz@redhat.com>

On Wed, Jun 30, 2004 at 11:20:02PM -0500, Benjamin Kosnik wrote:
> 
> >> I ran into this while rebuilding under the 3.4.1 prerelease:
> 
> There is no std::__default_alloc_template in gcc 3.4.x. 
> 
> This particular symbol comes from gcc-3.3.x, so this problem is a result
> of trying to mix-match 3.3.x and 3.4.x binaries, which is strictly
> prohibited.

I agree that the error message doesn't make much sense in this context. 
But what about the change in __pool_alloc?

-- 
Daniel Jacobowitz

Follow-Ups:
- Re: c++ link incompatibility between 3.4.0 and 3.4.1-20040625
  - From: Benjamin Kosnik

References:
- c++ link incompatibility between 3.4.0 and 3.4.1-20040625
  - From: Nick Rasmussen
- Re: c++ link incompatibility between 3.4.0 and 3.4.1-20040625
  - From: Mark Mitchell
- Re: c++ link incompatibility between 3.4.0 and 3.4.1-20040625
  - From: Benjamin Kosnik

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