[yocto] [meta-freescale] Compile error for boost_1.54.0

[Khem Raj]

On Jul 9, 2013, at 8:17 PM, Saul Wold <sgw at linux.intel.com> wrote:

> On 07/09/2013 01:50 PM, Martin Jansa wrote:
>> On Tue, Jul 09, 2013 at 09:25:30PM +0100, Chris Tapp wrote:
>>> Forwarding to Yocto mailing list:
>>> 
>>> On 9 Jul 2013, at 21:21, Otavio Salvador wrote:
>>> 
>>>> On Tue, Jul 9, 2013 at 5:19 PM, Chris Tapp <opensource at keylevel.com> wrote:
>>>>> 
>>>>> On 9 Jul 2013, at 20:09, Chris Tapp wrote:
>>>>> 
>>>>>> I'm getting a failure in do_compile when building boost_1.54.0 using master-next for the wandboard-quad.
>>>>>> 
>>>>>> The log is about 1.5MB, but the important bit seems to be that uintptr_t isn't defined but is required by /boost/atomic/atomic.hpp.
>>>>>> 
>>>>>> Has anyone seen this before?
>>>>> 
>>>>> I also meant to say that adding:
>>>>> 
>>>>> typedef unsigned long long uintptr_t;
>>>>> 
>>>>> to atomic.hpp 'fixes' the build, but this is not a good solution ;-)
>>>> 
>>>> It needs to be checked against normal Poky to ensure it is BSP
>>>> specific; I doubt it is.
>> 
>> See
>> http://lists.openembedded.org/pipermail/openembedded-devel/2013-July/091331.html
>> 
>> But maybe it wasn't caused by eglibc upgrade (and header cleanup in
>> eglibc) but by boost upgrade.
>> 
> I did the boost update and with the older eglibc, which is why it seemed to work for me.
> 
> I just did another build with the updated boost and both eglibc version 2.17 and 2.18, seems like the 2.18 version causes this breakage, as it built fine with 2.17, I also tried to revert the boost updated and build the older boost with 2.18 and it worked.
> 
> So it must be something with the newer boost and eglibc in combination, more digging is required.
> 

its related to https://bugzilla.yoctoproject.org/show_bug.cgi?id=4812


> Sau!
> 
>> 
>> 
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>