This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: 2.95.2 libraries donŽt link using 3.x
- From: Oscar Fuentes <ofv at wanadoo dot es>
- To: Miguel Angel Núñez <miguel dot nunez at datatronics dot es>
- Cc: gcc-help at gcc dot gnu dot org
- Date: 18 Jul 2002 19:23:45 +0200
- Subject: Re: 2.95.2 libraries donŽt link using 3.x
- References: <889130080.20020718191748@datatronics.es>
- Reply-to: gcc-help at gcc dot gnu dot org
Miguel Angel Núñez <miguel.nunez@datatronics.es> writes:
> Hello GCC experts,
>
> I hope you can help me in this link problem that I donŽt know how to
> solve.
>
> I'm using some libraries that were developed for GCC 2.95.2. I was
> using GCC 2.95.3 and everything was fine. My application was compiled
> and linked perfectly.
>
> Now I have to use GCC 3.x because of some source code I'm including
> from www.vovida.org that needs this version of GCC. The application
> is compiled, but at link time I get a lot of errors about undefined
> symbols (all of them in the libraries for 2.95.2).
>
> My question:
> Is there any modifier for having backwards compatibility? Compile
> 3.x code, and link against 3.x libraries and 2.95.2 libraries.
>
> Is this possible?
I guess you are talking about C++ (remember: GCC is 5 languages or so)
The C++ ABI changed on gcc 3.0.x The new ABI and the previous one are
incompatible.
>
> Any other idea about how to overcome this problem is very welcome.
You must re-build all your libraries with gcc 3.x if you want to use
it. Those binaries will not be compatible with gcc < 3.0
--
Oscar