Linking: dwarf error: mangled line number section.

Question

Hi,
I'm trying to get at 1st a unit test running (Suse 9.2, CC: Sun C++ 5.9 Linux_i386 Build35_2 2006/12/04). To keep things simple I start with only instantiation of a class of ccpunit:
int main(int argc, char* argv[] )
// Create the event manager and test controller
CPPUNIT_NS::TestResult controller;
In linking I get this error message:
COM_TestMain.o(.text+0x10a3)/usr/bin/ld: Dwarf Error: mangled line number section.
: In function `main':
: undefined reference to `CppUnit::TestResult::TestResult(CppUnit::SynchronizedObject::SynchronizationObject*)'
COM_TestMain.o(.text+0x10af): In function `main':
: undefined reference to `CppUnit::TestResult::~TestResult()'
dmake: Fatal error: Command failed for target `test.bin'
I translated cppunit also from source level with sunstudio compiler, but it makes no difference. The mentioned symbols seems to be there (look into libcppunit.a with objdump). An interesting question also would be, why this lib (and others) only build the static targets?
Does anybody know, what that error means and how to workaround? I'll also continue to find out and tell here in case of success.
Ciao, Rolf

Answer 1

Ok, finally I got that working. The reason for unresolveds was a wrong sequence in link statement:
working: $(CC) $(ARC_FLAGS) $(OBJECTS) $(CPPUNITLIB) $(LIBS)
not working: $(CC) $(ARC_FLAGS) $(CPPUNITLIB) $(OBJECTS) $(LIBS)
for some reasons in solaris/sparc world this was no matter.
But there is another problem with syntax in $(CPPUNITLIB), to me these two statements should do same:
CPPUNITLIB = $(CPPUNIT_HOME)/lib/libcppunit.a
CPPUNITLIB = -L$(CPPUNIT_HOME)/lib -Bstatic -lcppunit
If I'm using the last one, I get the "dwarf error" and also lots of warnings like this appear:
/usr/bin/ld: Warning: size of symbol `std::string &std::string::operator=(constchar*)' changed from 482 in /opt/sunstudiomars/prod/lib/libCstd.a(instance.o) to 475 in /opt/sunstudiomars/prod/lib/libCstd.a(instance.o).
The first syntax does link without any errors or warnings. But the created binaray finally is doing its job (in both cases :-) .
Ciao, Rolf