Re: Yocto 1.7_M2 release candidate 1 ready for QA

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2014-08-05 at 11:00 +0100, Richard Purdie wrote:
> On Fri, 2014-08-01 at 23:10 -0300, João Henrique Ferreira de Freitas
> wrote:
> > 
> > Hi,
> > 
> > I've tested all toolchains available at
> > http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/
> > 
> > My test program is very simple: 
> > 
> > --- c.cpp ---
> > #include <limits>
> > 
> > int main() {}
> > ---
> > 
> > Two considerations 
> > 
> > 1) the of ppce500v2-toolchain-1.6+snapshot.sh and
> > armv7a-vfp-neon-toolchain-1.6+snapshot.sh is less than others
> > toolchains
> > 
> > 2) when I try to compile c.cpp, using ppce500v2 or armv7a I get:
> > 
> > source /opt/poky/1.6
> > +snapshot/environment-setup-ppce500v2-poky-linux-gnuspe
> > $CXX c.cpp
> > 
> > In file included from c.cpp:2:0:
> > /opt/poky/1.6
> > +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> > ++/4.9.0/limits:42:28: fatal error: bits/c++config.h: No such file or
> > directory
> >  #include <bits/c++config.h>
> > 
> > I can't figure out what happened with these two toolchains.
> 
> You can fix the ppc toolchain with 
> "ln -s powerpc-poky-linux-gnuspe sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/4.9.0/powerpc-poky-linux"

I also couldn't reproduce this with the armv7 toolchain. Do you have the
logs from that failure?

Cheers,

Richard