[ILUG] linking 2.95 libraries with 3.2 compiled objects

[P at draigBrady.com]

Greg Farrell wrote:
> Hi guys,
> 
>   I've always thought you can't link a library compiled with g++2.95
> with one compiled with 3.2. So I've stuck to one version of the compiler
> for everything.
> 
> However a customer uses g++3.2. So we have to give them our libraries
> built using this version of the compiler. But the only version of a
> third-party closed source library one of our components depends on that
> we can download refuses to link with a 3.2 compiled object. I'm guessing
> this third party library is compiled with an earlier version of g++.
> 
> So, are we stymied? Is it a case of telling the customer use gcc-2.95 or
> naff off. Or am I being a bit silly?

You mention g++ so I presume the c++ ABI is at issue here?
http://gcc.gnu.org/gcc-3.2/c++-abi.html
In summary you're fecked.

-- 
Pádraig Brady - http://www.pixelbeat.org
--- Following generated by rotagator ---

rsync really is worth knowing. Here are two common uses.

To only get differences between file on the remote and
local server. For e.g. if you're having problems downloading,
you can run this several times to get the file.

rsync -P rsync://rsync.server.com/path/to/file file

This would copy file1 to file2 at around 1 MByte/s
Think of it as nice for I/O.

rsync --bwlimit=1000 file1 file2
--