|Linking with different compilers firstname.lastname@example.org (2004-08-23)|
|Re: Linking with different compilers email@example.com (Paul Pluzhnikov) (2004-08-25)|
|Re: Linking with different compilers firstname.lastname@example.org (Unknown) (2004-08-25)|
|Re: Linking with different compilers email@example.com (2004-09-03)|
|Date:||25 Aug 2004 14:54:15 -0400|
|Posted-Date:||25 Aug 2004 14:54:15 EDT|
I had a similar problem at work not long ago. We ended up convincing
the vendor to recompile with gcc 3.3 after trying fake the
libstdc++.so.3 by symlinking it from libstdc++.so.5. Unfortunately
encountered symbol changes from libstdc++.so.3 to libstdc++.so.5.
I am not sure if you can statically link in the code.
One possible way out of this conundrum is to wrap each library as a
RPC/CORBA server and make method calls between them as needed. I must
admit it is not the nicest of solutions.
Best of luck
On Mon, 23 Aug 2004 12:11:26 -0400, Bill wrote:
> I have some libraries from one vendor that was built with gcc 3.0.2. I
> have another set of libraries from another vendor that was built with
> gcc 3.3.
> I need to link a program that uses both libraries. I can get the two
> vendors stuff to link finally, but I'm having trouble with libstdc++
> and libgcc_s. ...
Return to the
Search the comp.compilers archives again.