Displaying 3 results from an estimated 3 matches for "pr1860".
Did you mean:
pr18860
2008 Jun 13
2
[LLVMdev] Type conflicts with linkonce functions
...39;item.o.bc': Function
'_ZN18st_select_lex_unit12first_selectEv' defined as both '
%struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)' and '
%struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)'
I encountered the above while building mysql 5.0.51a after
dealing with PR1860 - some of the source files appear to have slightly
different definitions of the same type name, which makes the error
message especially confusing. In any case, this doesn't seem right - I
would expect the link to proceed regardless of the type mismatch. The
patch below is intended to c...
2008 Jun 20
0
[LLVMdev] Type conflicts with linkonce functions
...> '_ZN18st_select_lex_unit12first_selectEv' defined as both '
> %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)' and '
> %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)'
>
> I encountered the above while building mysql 5.0.51a after
> dealing with PR1860 - some of the source files appear to have
> slightly different definitions of the same type name, which makes
> the error message especially confusing. In any case, this doesn't
> seem right - I would expect the link to proceed regardless of the
> type mismatch. The patch be...
2008 Jul 09
1
[LLVMdev] Type conflicts with linkonce functions
..._ZN18st_select_lex_unit12first_selectEv' defined as both '
>> %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)' and '
>> %struct.SELECT_LEX* (%struct.SELECT_LEX_UNIT*)'
>>
>> I encountered the above while building mysql 5.0.51a after
>> dealing with PR1860 - some of the source files appear to have
>> slightly different definitions of the same type name, which makes
>> the error message especially confusing. In any case, this doesn't
>> seem right - I would expect the link to proceed regardless of the
>> type mismatch. The...