On Jul 9, 2013, at 1:50 PM, Martin Jansa <martin.ja...@gmail.com> 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 <opensou...@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 in above thread answering to your question if you want to include <cstblib> you need to specify -std=gnu++0x or -std=c++0x to cppflags. above container is not supported prior to c++0x standard > > But maybe it wasn't caused by eglibc upgrade (and header cleanup in > eglibc) but by boost upgrade. > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto