From b7337a119993d0923968fbaa3e4539a6c701706f Mon Sep 17 00:00:00 2001 From: Tristan Van Berkom Date: Thu, 5 May 2016 23:52:11 +0100 Subject: [PATCH 9/9] gcc-cross-initial: Fixing build on aarch64 When building on aarch64 targetting aarch64, the gcc-cross-initial stage bails out in configure-target-libgcc while trying to use the in tree compiler which has not yet been produced by all-gcc. Upstream yocto bug report and patch mail: https://bugzilla.yoctoproject.org/show_bug.cgi?id=9510 http://lists.openembedded.org/pipermail/openembedded-core/2016-April/120669.html --- meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend diff --git a/meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend b/meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend new file mode 100644 index 0000000..b6513b9 --- /dev/null +++ b/meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend @@ -0,0 +1,7 @@ +# For some reason on aarch64 building for aarch64, we need +# to run the two make targets separately otherwise the in-tree +# gcc/xgcc is not ready for configure-target-libgcc +do_compile () { + oe_runmake all-gcc + oe_runmake configure-target-libgcc +} -- 2.7.4