Re: [boost] [wave] Recent check-ins broke wave onTru64/CXX/RC_1_34_0

From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2007-01-23 11:16:14

Markus Schoepflin wrote:
> Boris Gubenko wrote:
>> Hartmut Kaiser wrote:
>>> Is there a tool to unmangle the names?
>>
>> nm -mangled_name_also *.o | grep symbol_reported_as_multiply_defined
>
> This doesn't give any output. "demangle" return just the mangled name. Is
> there some length limitation to nm or demangle? Or some sort of name
> compression scheme that those tools don't understand?

The names are indeed very long, but nm works for me on Tru64 V5.1 2650.
On my Tru64 machine, the compiler runs out of memory when compiling some
wave library modules, so I cannot reproduce the link failure.

Did you run nm on the wave library object files (e.g.
instantiate_defined_grammar.o) or on object files in the repository? The muldefs 
may come from the latter.

After more thinking about it, it occurred to me, that by default, ld
(prelink) actually reports original, non-mangled, source-code names.
>From cxx manpage:

  -nodemangle
       Causes linker messages to contain mangled names.  By default, names
       are mangled in both Tru64 UNIX and Linux Alpha.

So, the names in http://tinyurl.com/ysqbex should be original names and
you, probably, don't need nm or demangle. The names do look strange:
__CPR475__new_lexer__...lex_token<Z2Z>

Boris

----- Original Message ----- 
From: "Markus Schöpflin" <markus.schoepflin_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Tuesday, January 23, 2007 10:03 AM
Subject: Re: [boost] [wave] Recent check-ins broke wave onTru64/CXX/RC_1_34_0

> Boris Gubenko wrote:
>> Hartmut Kaiser wrote:
>>> Is there a tool to unmangle the names?
>>
>> nm -mangled_name_also *.o | grep symbol_reported_as_multiply_defined
>
> This doesn't give any output. "demangle" return just the mangled name. Is
> there some length limitation to nm or demangle? Or some sort of name
> compression scheme that those tools don't understand?
>
>
>> 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.
>
> Other parts of boost depend on the control given by -timplicit_local, I
> even have no idea if spirit would work with -tlocal.
>
> Hartmut, did you recently add some manually instantiated templates to wave?
> If yes, please have a look at the CXX workaround in
> 'boost/test/utils/trivial_singleton.hpp' to see if it helps in any way.
>
> Markus
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
>