Re: undefined symbols using StlPort 4.6 and g++ 3.3

[Paul Pluzhnikov]

mhunley@san.rr.com (Michael Hunley) writes:

> I have also verified that the undefined
> symbols are in the libstlport_gcc.a located there using nm with
> --demangle and that they are externed.  

Now verify that they are *really* there without the --demangle:
it is often the case that differently-mangled symbols demangle to
the same name. (You can find out mangled names for the missing
symbols with e.g. 'nm build/MohoHashtest.o | grep wcerr').

Was the libstlport_gcc.a compiled with the exact same version of g++?
Chances are, it wasn't. There have been ABI changes/fixes, which made
g++-3.0, 3.1, 3.2 and 3.3-compiled code link-incompatible.

Cheers,
-- 
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.