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

[Martin Beaudoin]

Andreas Jaeger wrote:

>Martin Beaudoin <beaudoin.martin@ireq.ca> writes:
>
>  
>
>>Hello,
>>
>>I am experiencing some STL compatibility problems between
>>
>>g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
>>
>>and
>>
>>g++ (GCC) 3.3 20030226 (prerelease) (SuSE Linux 8.2)
>>
>>
>>I have a library compiled with g++ version 3.3 on Suse 8.2. The
>>library is making heavy use of STL.
>>
>>When I link this library with a program compiled with gcc 3.2 on
>>RedHat 8.0,  the linker complains about the
>>    
>>
>
>
>  
>
>>undefined reference to `std::__default_alloc_template<(bool)1,
>>(int)0>::_S_force_new'
>>    
>>
>
>On which system do you execute this?  You need the libstdc++ from GCC
>3.3 for this installed on the system.  Or expressed differently:
>Executing your program should work on the SuSE system but fail on the
>Red Hat system.
>
>Andreas
>  
>
Exactly, the linking problems occurs only on the GCC 3.2 based RedHat 
systems.

I know that I need to install libstdc++ from GCC 3.3 on my GCC 3.2 based 
RedHat systems, but not only for running the program; I also need to 
link the program on the RedHat system.

I would prefer instead to harmonize both development platforms to one 
and only one compiler major version (let's say 3.x).

But gcc 3.3 and gcc 3.2 only differs by a minor version number .  

I would expect compatibility between minor version changes (let's say 
3.2 and 3.3), and probable or "youbetcha" incompatibilities between 
major versions  (2.x and 3.x).

Do you have any insight about the CVS Attic problem?

Martin


-- 
Martin Beaudoin, M.Sc.A., ing.             beaudoin.martin@ireq.ca
Chercheur
Institut de recherche d'Hydro-Quebec(IREQ)
Analyse et gestion de reseaux
1800 boul. Lionel Boulet                       tel: (450) 652-8235
Varennes (Quebec) J3X 1S1 Canada               fax: (450) 652-8309