linking against c++ shared library built using autoconf (and libtool)

[Wil Turner <wturner@xxxxxxxxxxxxxx>]

I have a project that has recently been converted to using autoconf as 
a build system. The primary product of the project is a c++ shared 
library. Using autoconf, the library appears to build and install 
correctly, but when attempting to run another executable that has been 
linked against it, ld spits out the following:

dyld: ./calculator Undefined symbols:
__ZTVN10__cxxabiv117__class_type_infoE
___cxa_pure_virtual
___gxx_personality_v0
__ZTVN10__cxxabiv121__vmi_class_type_infoE
Trace/BPT trap

I'm currently building on MacOS X 10.3.

Looking over the output when the library is built, I notice that all of 
the link steps are done using gcc instead of g++, but I'm not sure 
where to change this in configure.ac; g++ *is* used for the .cc -> .o 
steps. Is there a variable that can be set to change the compiler used 
for these steps, or am I doing something else wrong? The documentation 
doesn't seem to mention this problem at all.

Wil



_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf