Link error in Workshop 6u2 with lib built by Studio 9

Question

I have a shared library built with Sun Studio 9.
I'm trying to use it in an application that I build using Sun
Workshop 6 update 2.
This gives me a link error:
Undefined symbol first referenced in file
__rwstd::__null_string_ref_rep<char,std::char_traits<char>,
std::allocator<char>,__rwstd::__string_ref_rep<std::allocator<char>
>>::__null_string_ref_rep()
/home/me/lib/libFoo.so
std::basic_string<char,std::char_traits<char>,std::allocator<char>>::~basic_string()
/home/me/lib/libFoo.so
The lib is built using:
JAVA_INCLUDE = -I${JAVA_HOME}/include -I${JAVA_HOME}/include/solaris
JAVA_LIBS = -L${JAVA_HOME}/jre/lib/sparc -L${JAVA_HOME}/jre/lib/sparc/client
CXX = g++
CXXFLAGS = -g -w -fPIC -I./include ${JAVA_INCLUDE}
LDFLAGS = -shared ${JAVA_LIBS} -ljava -ljvm
$(CXX) ${LDFLAGS} ${LIBS} -o ../$@ ${OBJS}
Any ideas what could be wrong?
Thanks in advance,
/Mikael

Answer 1

You can use a binary created by an older compiler in a program built with a newer compiler. We take care not to invalidiate old binary interfaces in new compilers.
You cannot use a binary created by a newer compiler in a program built with an older compiler. The newer compiler will in general use features from headers or system libraries that are unknown to the older compiler.
If you have a set of binaries created by different compiler versions, you must build the final program using a compiler at least as new as the newest compiler that was used.
Similar rules apply to verions of Solaris where the binaries are built. If you build a binary on an older Solaris version, you can use it on a newer Solaris version -- but not the reverse.