From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: Is target toolchain supposed to be working?
Date: Tue, 19 Jun 2012 14:32:10 +0200 [thread overview]
Message-ID: <4FE0714A.1060603@linaro.org> (raw)
In-Reply-To: <4FE0684D.2000906@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
W dniu 19.06.2012 13:53, Marcin Juszkiewicz pisze:
> ignoring nonexistent directory "usr/include/c++/"
> ignoring nonexistent directory "usr/include/c++//i586-oe-linux"
> ignoring nonexistent directory "usr/include/c++//backward"
> ignoring nonexistent directory "/usr/local/include"
> ignoring nonexistent directory
> "/usr/lib/gcc/i586-oe-linux/4.7.1/../../../../i586-oe-linux/include"
> #include "..." search starts here:
> .
> #include <...> search starts here:
> ..
> ../lib
> /usr/lib/gcc/i586-oe-linux/4.7.1/include
> /usr/lib/gcc/i586-oe-linux/4.7.1/include-fixed
> /usr/include
> ../lib/compat
> End of search list.
Attached patch fixed problem for me.
[-- Attachment #2: 0001-gcc-make-sure-that-c-includes-will-be-found.patch --]
[-- Type: text/x-patch, Size: 1984 bytes --]
From 56382cac2c337f9e620d538f8697737b2ca777cf Mon Sep 17 00:00:00 2001
From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date: Tue, 19 Jun 2012 14:30:06 +0200
Subject: [PATCH] gcc: make sure that c++ includes will be found
Without this patch g++ was not able to find headers:
ignoring nonexistent directory "usr/include/c++/"
ignoring nonexistent directory "usr/include/c++//i586-oe-linux"
ignoring nonexistent directory "usr/include/c++//backward"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory
"/usr/lib/gcc/i586-oe-linux/4.7.1/../../../../i586-oe-linux/include"
.
..
../lib
/usr/lib/gcc/i586-oe-linux/4.7.1/include
/usr/lib/gcc/i586-oe-linux/4.7.1/include-fixed
/usr/include
../lib/compat
End of search list.
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
---
meta/recipes-devtools/gcc/gcc-4.7.inc | 2 +-
meta/recipes-devtools/gcc/gcc-configure-target.inc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-devtools/gcc/gcc-4.7.inc
index 34a73b1..077419c 100644
--- a/meta/recipes-devtools/gcc/gcc-4.7.inc
+++ b/meta/recipes-devtools/gcc/gcc-4.7.inc
@@ -1,6 +1,6 @@
require gcc-common.inc
-PR = "r2"
+PR = "r3"
# Third digit in PV should be incremented after a minor release
# happens from this branch on gcc e.g. currently its 4.7.0
diff --git a/meta/recipes-devtools/gcc/gcc-configure-target.inc b/meta/recipes-devtools/gcc/gcc-configure-target.inc
index b2f91b7..25fceb5 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-target.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-target.inc
@@ -3,4 +3,4 @@ require gcc-configure-common.inc
EXTRA_OECONF_PATHS = " \
--with-sysroot=/ \
--with-build-sysroot=${STAGING_DIR_TARGET} \
- --with-gxx-include-dir=${includedir}/c++/"
+ --with-gxx-include-dir=/${includedir}/c++/"
--
1.7.10.4
next prev parent reply other threads:[~2012-06-19 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 11:53 Is target toolchain supposed to be working? Marcin Juszkiewicz
2012-06-19 12:32 ` Marcin Juszkiewicz [this message]
2012-06-19 16:19 ` Khem Raj
2012-06-19 16:25 ` Marcin Juszkiewicz
2012-06-20 7:55 ` Khem Raj
2012-06-20 12:12 ` Marcin Juszkiewicz
2012-06-20 15:06 ` Khem Raj
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=4FE0714A.1060603@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox