Link problems

[Oscar Fuentes]

bjorn rohde jensen <bjensen@fastmail.fm> writes:

> Hi Jarmo,
> 
>  You can not in general crosslink object code generated by
> different compilers. You should use one and only one
> compiler to create an application. One does usually not
> have to rebuild the system C libraries, but C++ libs etc
> definitely should be.
>  The unresolved symbols are probably due to different
> name mangling schemes employed by gcc-2.96, which is not
> actually an official gcc release, and gcc-3.0.4. This is
> done to protect users from linking incompatible object
> files to create applications with spectacularly odd behaviour,
> such as random core dumps despite code correctness and so on.

Actually, that incompatibility among gcc 2.9x and gcc 3.x comes from
the introduction of a new "standard" C++ ABI on the gcc 3.x
series. One of the main goals of the new ABI is to allow the
interchange of object code among different C++ compilers which use
said ABI.

-- 
Oscar