From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: Yocto 1.7_M2 release candidate 1 ready for QA
Date: Fri, 01 Aug 2014 23:10:14 -0300 [thread overview]
Message-ID: <53DC4886.8070406@gmail.com> (raw)
In-Reply-To: <CFFE70D2.703B%alexandru.c.georgescu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2981 bytes --]
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
<http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/poky-eglibc-x86_64-core-image-sato-ppce500v2-toolchain-1.6+snapshot.sh>
and armv7a-vfp-neon-toolchain-1.6+snapshot.sh
<http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1/toolchain/x86_64/poky-eglibc-x86_64-core-image-sato-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.
Thanks.
On 30-07-2014 03:52, Georgescu, Alexandru C wrote:
> Ha, nice to see green here! :)
> --
> Alexandru Georgescu
> Yocto QA Engineer
> SSG/SSD Open Source Technology Center Romania
>
>
>
>
> On 30/07/14 09:41, "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
> wrote:
>
>> Full green build!
>>
>> http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M2.rc1
>>
>> bitbake 4aaf56bfbad4aa626be8a2f7a5f70834c3311dd3
>> eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
>> eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
>> meta-fsl-arm 6ef8db67df3436a463851ff95dcfb6a66132f3c0
>> meta-fsl-ppc 5efa2d27dcf4637b008faf782b5e257b748b24c0
>> meta-intel 67b7f6f3a03ddbdcf66823eb5a236edbc0aa4858
>> meta-minnow ee48eba5895178ec19febee2e0a2d8b0f3ace0e9
>> meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
>> oecore 7986adeac16550b33f65fded39a55f668e0e543f
>> poky 2d1660112e54653f7bb763939d0416472c49fe01
>>
>>
>> --
>> Elizabeth Flanagan
>> Yocto Project
>> Build and Release
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
[-- Attachment #2: Type: text/html, Size: 4187 bytes --]
next prev parent reply other threads:[~2014-08-02 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 6:41 Yocto 1.7_M2 release candidate 1 ready for QA Flanagan, Elizabeth
2014-07-30 6:52 ` Georgescu, Alexandru C
2014-08-02 2:10 ` João Henrique Ferreira de Freitas [this message]
2014-08-05 9:05 ` Richard Purdie
2014-08-05 11:15 ` João Henrique Ferreira de Freitas
2014-08-06 3:10 ` João Henrique Ferreira de Freitas
2014-08-05 10:00 ` Richard Purdie
2014-08-05 10:32 ` Richard Purdie
2014-08-05 11:22 ` João Henrique Ferreira de Freitas
2014-08-05 14:49 ` Georgescu, Alexandru C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53DC4886.8070406@gmail.com \
--to=joaohf@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.