Backport of gcc header fix from master/dizzy

I made this backport earlier but missed actually sending it.

The following change since commit 5a577ec878a15f3caaf4893b819825ffb8c81266:

build-appliance-image: Update to daisy head revision (2015-05-13 13:27:45 +0100)

is available in the git repository at:

git://git.openembedded.org/openembedded-core-contrib paule/gcc-omp-fix-daisy
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/gcc-omp-fix-daisy

Paul Eggleton (1):
gcc: ensure target gcc headers can be included

 meta/recipes-devtools/gcc/gcc-4.8.inc              |  1 +
 .../gcc/gcc-4.8/target-gcc-includedir.patch        | 81 ++++++++++++++++++++++
 2 files changed, 82 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.8/target-gcc-includedir.patch

2.1.0

There are a few headers installed as part of gcc-runtime (omp.h, ssp/*.h). Being installed from a recipe built for the target architecture, these are within the target sysroot and not cross/nativesdk; thus they weren't able to be found by gcc with the existing search paths. Add support for picking up these headers under the sysroot supplied on the gcc command line in order to resolve this.

Thanks to Richard Purdie for giving me a number of pointers during fixing this issue.

Fixes [YOCTO #7141].

(From oe-core master rev: 5c87bb9ac2b35b3f8cf2b7d3e4507e7013115162)

---
 meta/recipes-devtools/gcc/gcc-4.8.inc              |  1 +
 .../gcc/gcc-4.8/target-gcc-includedir.patch        | 81 ++++++++++++++++++++++
 2 files changed, 82 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.8/target-gcc-includedir.patch

index f7d7bec..87e6908 100644
@@ -72,6 +72,7 @@ SRC_URI = "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.bz2 \
 	   file://0049-Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch \
 	   file://0050-PR-target-58595.patch \
 	   file://0051-fix-unwind-race.patch \
+	   file://target-gcc-includedir.patch \
 	  "
 SRC_URI[md5sum] = "a3d7d63b9cb6b6ea049469a0c4a43c9d"
 SRC_URI[sha256sum] = "09dc2276c73424bbbfda1dbddc62bbbf900c9f185acf7f3e1d773ce2d7e3cdc8"

2.1.0

Now that 1.6.3 is out can we look at merging this?

Thanks,
Paul

Paul Eggleton
Intel Open Source Technology Centre