Hartmut Kaiser wrote:
Is there a tool to unmangle the names?
nm -mangled_name_also *.o | grep symbol_reported_as_multiply_defined Markus, the problem may go away if you compile -tlocal instead of -timplicit_local, but you, probably, would not want to change instantiation mode just for one library. Boris ----- Original Message ----- From: "Hartmut Kaiser" <hartmut.kaiser@gmail.com> To: <boost@lists.boost.org> Sent: Tuesday, January 23, 2007 8:55 AM Subject: Re: [boost] [wave] Recent check-ins broke wave onTru64/CXX/RC_1_34_0
Markus,
The compilation of wave actually succeeds, but linking libboost_wave-d-1_34.so.1.34.0 complains about multiply defined symbols. See http://tinyurl.com/ysqbex for further details.
This has been broken recently (not more than 2 weeks ago) and I noticed that there are some check-ins related to wave in this time frame.
Does that ring a bell with anyone?
BTW, there are two references to 1.34 in the name of the generated library. Is that how it's supposed to be? Isn't the 1.34.0 suffix after .so somehow wrong?
Is there a tool to unmangle the names? This could help me finding a clue what's wrong.
Regards Hartmut
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost