./libstdc++-v3/include/bits/stl_alloc.h : Incompatibility between g++ 3.3 and g++ 3.2?

[Andreas Jaeger]

Benjamin Kosnik <bkoz@redhat.com> writes:

>>Now, as for my incompatibilitiy problem (stl_alloc.h is not downward 
>>compatible from g++ 3.3 to g++ 3.2), the only solution I can see is that 
>>I need to standardize my development Linux stations over one and only 
>>one g++ compiler version. 
>
> You are confused. There is only upward compatibility, ie 3.2 links with
> -> 3.3, not the other way around. Thus, if you are compiling with 3.3,
> you'll need to link to 3.3. If you compile with 3.2.x, you'll be able to
> link with 3.2.x or 3.3.x.
>
> I believe Andreas answered this question also, indicating that it should
> go in our docs. I'll work on updating them over the weekend.

A general webpage mentioning the C++ compatibility issues, including
libstdc++ would be much appreciated.  See also my email on the main
GCC list today for some points that should be answered in more depth
than I did so far.

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20030905/964d1f8c/attachment.sig>