diff options
author | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2016-05-05 23:52:11 +0100 |
---|---|---|
committer | Alexander Larsson <alexl@redhat.com> | 2016-05-06 12:14:02 +0200 |
commit | 4d54ef4090a1c504d0c7f81acbd2817044f990c3 (patch) | |
tree | 937c5b05e885d9e65ee9597fe12d148762952f60 | |
parent | db6c10cfd88650bb0e21aa8f1b3bcdb3cf54da3f (diff) |
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
-rw-r--r-- | meta-freedesktop/recipes-devtools/gcc/gcc-cross-initial_%.bbappend | 7 |
1 files changed, 7 insertions, 0 deletions
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 +} |