[yocto] Yocto 1.7_M2 release candidate 1 ready for QA

[Richard Purdie]

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.
> 
> # find /opt/poky/1.6+snapshot/ -name c++config.h
> [sudo] password for joaohf: 
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c
> ++/4.9.0/powerpc-poky-linux-gnuspe/bits/c++config.h
> /opt/poky/1.6
> +snapshot/sysroots/ppce500v2-poky-linux-gnuspe/usr/src/debug/gcc-runtime/4.9.0-r0/gcc-4.9.0/build.powerpc-poky-linux-gnuspe.powerpc-poky-linux-gnuspe/powerpc-poky-linux-gnuspe/libstdc++-v3/include/powerpc-poky-linux-gnuspe/bits/c++config.h
> 
> Someone has any hint?
> 
> I suspect something at meta-fsl-ppc and meta-fsl-arm.
> 
> 
> Is there QA tests against toolchains? I think there is nice to have
> one. Like installs all toolchain locally and use each one to compile
> something.
> 

Just to let you know this email is useful thanks and there is something
being done about this. Alex is looking into why our testing hasn't shown
up the problem. If these are the meta-fsl toolchains, its likely our
test coverage doesn't extend to those and that is why the issue has been
missed. There is only so much testing we can do on a regular basis.

Ultimately we plan to automate the testing of the toolchains but that is
something we continue to work towards, its not ready yet.

On the specific errors, I think its likely the fact we're using one
compiler over multiple different configurations and there is likely some
kind of path issue somewhere. It may be worth filing bugs on these
issues to ensure they don't get lost.

Thanks again for pointing out the problem though, it is something that
needs to get fixed (and we need to improve the automated test coverage).

Cheers,

Richard