Re: failed build after rev b646413c3d0e

[Ben Abbott]

On Sep 1, 2011, at 12:16 PM, Andreas Weber wrote:

> Am 01.09.2011 00:12, schrieb Ben Abbott:
>> 
>> On Aug 31, 2011, at 5:05 PM, Andreas Weber wrote:
>>> address@hidden:~/src$ nm --demangle
>>> ./build_octave/liboctave/.libs/liboctave_la-Sparse-C.o|grep "::Sparse(Perm"
>>> 0000000000000000 W Sparse<bool>::Sparse(PermMatrix const&)
>>> 0000000000000000 W Sparse<double>::Sparse(PermMatrix const&)
>>> address@hidden:~/src$ nm --demangle
>>> ./build_octave/liboctave/.libs/liboctave_la-Sparse-b.o|grep "::Sparse(Perm"
>>> 0000000000000000 W Sparse<bool>::Sparse(PermMatrix const&)
>>> 0000000000000000 W Sparse<double>::Sparse(PermMatrix const&)
>>> 
>>> Andy
>> 
>> I'm not familiar with what the output of nm implies.
>> 
>> Does it imply that the symbols (?) below are duplicates?
> 
> Hi Ben,
> I have to apologize because I didn't carry out my thoughts.
> 
> From the nm manpage:
> "W","w" The symbol is a weak symbol that has not been specifically
> tagged as a weak object symbol. When a weak defined symbol is linked
> with a normal defined symbol, the normal defined symbol is used with no
> error.  When a weak undefined symbol is linked and the symbol is not
> defined, the value of the symbol is determined in a system-specific
> manner without error. On some systems, uppercase indicates that a
> default value has been specified.
> 
> So I think I had no problem with linking because of the "weak" symbol
> even when it is defined twice. But I don't really know if ccache causes
> this flag.
> 
> Andy

Andy,

Thanks for the help. gcc on MacOS tends to be more pedantic than on most Lunix 
systems.

As a result, its often difficult to distinguish between a bug and the 
pedanticism (word?) of my compiler. Your quick response was helpful.

Thanks again.

Ben