Skip to contentSkip to conversation

gcc-4.5: Update gxx headers patch

PATCH In review Khem Raj 2 participants 2 messages Dec 21, 2011

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 gcc-4.5: Update gxx headers patch

This patch now expects gxx-include-dir
to be specified under sysroot which we
already do through gcc-cross4.inc from
oe-core

Please test

---
 meta-oe/recipes-devtools/gcc/gcc-4.5.inc           |    4 +-
 .../GPLUSPLUS_INCLUDE_DIR_with_sysroot.patch       |  177 ++++++++++++++++++--
 2 files changed, 163 insertions(+), 18 deletions(-)
meta-oe/recipes-devtools/gcc/gcc-4.5.inc +2 -2
index a0c2a7b..c2c451b 100644
@@ -14,7 +14,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
 
 
 PV = "4.5"
-PR = "r44"
+PR = "r45"
 
 # BINV should be incremented after updating to a revision
 # after a minor gcc release (e.g. 4.5.1 or 4.5.2) has been made
@@ -226,13 +226,13 @@ SRC_URI = "svn://gcc.gnu.org/svn/gcc/branches;module=${BRANCH};proto=http \
        file://fedora/gcc45-no-add-needed.patch;striplevel=0 \
        file://optional_libstdc.patch \
        file://64bithack.patch \
-       file://GPLUSPLUS_INCLUDE_DIR_with_sysroot.patch \
        file://COLLECT_GCC_OPTIONS.patch \
        file://gcc-poison-dir-extend.patch \
        file://gcc-poison-parameters.patch \
        file://gcc-ppc-config-fix.patch \
        file://use-defaults.h-and-t-oe-in-B.patch \
        file://gcc-with-linker-hash-style.patch \
+       file://GPLUSPLUS_INCLUDE_DIR_with_sysroot.patch \
        "
 
 # Language Overrides
meta-oe/recipes-devtools/gcc/gcc-4.5/GPLUSPLUS_INCLUDE_DIR_with_sysroot.patch +161 -16

194 lines not on this page · raw message

Signature · 1 line
1.7.5.4
Tested-by on v1 1/1
#1 lore raw
Quoted 8 lines · Khem Raj

This patch now expects gxx-include-dir
to be specified under sysroot which we
already do through gcc-cross4.inc from
oe-core

Please test

with this patch I manage again to succesful build some images which were sometimes failing with c++ header not found (especially with BB_THREAD_NUMER > 4). This doesn't explain why sometimes these image were building fine.