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

[Paul Pluzhnikov]

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

> The version of STLPort I build on solaris, then run nm
> on *does not* have these decorators.  

I've built STLport-4.6.2 using unmodified 'gcc-sun.mak' on
Solaris7/SPARC using gcc-3.3, and I do have the symbols you are
missing:

$ nm -A ../lib/libstlport_gcc.a | grep ios_base4Init | c++filt

../lib/libstlport_gcc.a:iostream.o:00000340 B _STL::ios_base::Init::_S_count
../lib/libstlport_gcc.a:iostream.o:00000010 T 
_STL::ios_base::Init::Init[in-charge]()
../lib/libstlport_gcc.a:iostream.o:00000000 T 
_STL::ios_base::Init::Init[not-in-charge]()
../lib/libstlport_gcc.a:iostream.o:00000030 T _STL::ios_base::Init::~Init 
[in-charge]()
../lib/libstlport_gcc.a:iostream.o:00000020 T _STL::ios_base::Init::~Init 
[not-in-charge]()

One difference is that my gcc-3.3 was built with
--with-gnu-as=/usr/local/bin/as --with-gnu-ld=/usr/local/bin/ld

> Why are they missing from the
> emitted symbols when I build STLPort, but included in the unresovled
> references when I compile the app source with the same environment?

Don't know.

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