> backround info: I'm building an application in standard compat=5 mode, Sun
> Workshop 5.0
> I have a set of 3rd party libraries which
> were built with Sun Workshop 4.2
> These libraries depend in libC. My application depends on libCrun.
> Question: Does it make sense to link both libC and libCrun ?
> When I try and link both libC
> and libCrun, I get multiply defined symbols,
> ie _ex_register defined in
> both libC and libCrun.
Linking together ARM (4.2 or -compat=4) C++ code
and ANSI/ISO (5.0 with -compat=4) C++ code will
usually *not* work, because of duplicate or
unresolved symbols at various places (the ABI is different).
The only way you could possibly get this to work is
- exception handling only either in the -compat=4 or the
-compat=5 part of the code (otherwise
duplicate symbols here, too)
- the interface between both parts is a pure C interface
Compare the C++ migration guide