I am having problems with undefined symbols using a May 16 pull and running under Tru64 5.0. When I run mozilla I get: 138624:./mozilla-bin: /sbin/loader: Error: Unresolved symbol in /tmp/jln/build/dist/bin/libxpcom.so: __vtbl_27basic_nsAWritableString__Tc 138624:./mozilla-bin: /sbin/loader: Error: Unresolved symbol in /tmp/jln/build/dist/bin/libxpcom.so: __vtbl_28basic_nsAWritableString__TUs 138624:./mozilla-bin: /sbin/loader: Fatal Error: this executable has unresolvable symbols and If I run these through the demangler I get: __vtbl_27basic_nsAWritableString__Tc Make sure that the first noninlined virtual member function of 'basic_nsAWritableString<char>' is defined. __vtbl_28basic_nsAWritableString<unsigned short>

With this mornings pull I only have 1 unresolved symbol: 169405:./mozilla-bin: /sbin/loader: Error: Unresolved symbol in /tmp/jln/build/dist/bin/libxpcom.so: __vtbl_27basic_nsAWritableString__Tc

I have a patch which uses cxx to create shared libs rather than using /usr/bin/ld. This is necessary if we want to use template repositories, and it does not hurt if we dont. Can I check this in Chris?

r=cls

Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

I forgot to close this bug when the code got fixed. The combination of using the cxx compiler to generate shared libs, and using a global template repository makes things work well.