Thread overview
warning: size of symbol changed
Feb 16, 2012
Ellery Newcomer
Feb 16, 2012
Ali Çehreli
Feb 16, 2012
Ellery Newcomer
Feb 16, 2012
Jacob Carlborg
Feb 16, 2012
Ellery Newcomer
February 16, 2012
has anyone else gotten warnings of the nature

/usr/bin/ld: Warning: size of symbol `{875charlongsymbol}' changed from 107 in multi_index.o to 99 in multi_index.o
February 16, 2012
On 02/15/2012 06:35 PM, Ellery Newcomer wrote:
> has anyone else gotten warnings of the nature
>
> /usr/bin/ld: Warning: size of symbol `{875charlongsymbol}' changed from
> 107 in multi_index.o to 99 in multi_index.o

This can happen if there are two object files that are compiled with different definitions of a type. Are there two multi_index.o files and the two are compiled conditionally to see e.g. a struct differently?

Ali
February 16, 2012
On 02/15/2012 10:03 PM, Ali Çehreli wrote:
> On 02/15/2012 06:35 PM, Ellery Newcomer wrote:
>> has anyone else gotten warnings of the nature
>>
>> /usr/bin/ld: Warning: size of symbol `{875charlongsymbol}' changed from
>> 107 in multi_index.o to 99 in multi_index.o
>
> This can happen if there are two object files that are compiled with
> different definitions of a type. Are there two multi_index.o files and
> the two are compiled conditionally to see e.g. a struct differently?
>
> Ali

Hmm. I don't think there are two of them, but there is some pretty heavy templating going on. Maybe.

It's just one compile with three files.
February 16, 2012
On 2012-02-16 03:35, Ellery Newcomer wrote:
> has anyone else gotten warnings of the nature
>
> /usr/bin/ld: Warning: size of symbol `{875charlongsymbol}' changed from
> 107 in multi_index.o to 99 in multi_index.o

Sounds like you should do a clean build.

-- 
/Jacob Carlborg
February 16, 2012
On 02/16/2012 01:32 AM, Jacob Carlborg wrote:
> On 2012-02-16 03:35, Ellery Newcomer wrote:
>> has anyone else gotten warnings of the nature
>>
>> /usr/bin/ld: Warning: size of symbol `{875charlongsymbol}' changed from
>> 107 in multi_index.o to 99 in multi_index.o
>
> Sounds like you should do a clean build.
>

it does this on a clean build.