Check libcc1 directory before trying to fix it
Signed-off-by: Daniel Gomez <daniel.gomez(a)silicon-gears.com>
---
meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb b/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb
index 3e0f4bc..5a26fa2 100644
--- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb
+++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb
@@ -10,7 +10,9 @@ ARM_INSTRUCTION_SET_armv4 = "arm"
do_configure_prepend() {
# Easiest way to stop bad RPATHs getting into the library since we have a
# broken libtool here
- sed -i -e 's/hardcode_into_libs=yes/hardcode_into_libs=no/' ${S}/libcc1/configure
+ if [ -d "${S}/libcc1" ]; then
+ sed -i -e 's/hardcode_into_libs=yes/hardcode_into_libs=no/' ${S}/libcc1/configure
+ fi
}
BBCLASSEXTEND = "nativesdk"
--
2.7.4
Koen, Fathi,
Thanks for updating gcc recipe to 7.2 and merging it to rocko! I have some
matching fixes for the external toolchain recipe I'll try to submit soon...
I was wondering what are the plans for other toolchain components, like glibc,
gdb and binutils - there are recipes for glibc 2.20-2014.11, gdb 7.8-2014.09
and binutils 2.25/2.27 2016.10. All those correspond to when the last time a
tarball of that component was released by Linaro. I know these days all those
components are in git at https://git.linaro.org/toolchain/ - are there any
plans to provide corresponding recipes to build those components from sources?
--
Denys