From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto 1.7_M2 release candidate 1 ready for QA
Date: Tue, 05 Aug 2014 11:00:46 +0100 [thread overview]
Message-ID: <1407232846.6981.77.camel@ted> (raw)
In-Reply-To: <53DC4886.8070406@gmail.com>
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"
Cheers,
Richard
next prev parent reply other threads:[~2014-08-05 10:01 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
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 [this message]
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=1407232846.6981.77.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=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.