aboutsummaryrefslogtreecommitdiffstats
path: root/meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend
diff options
context:
space:
mode:
authorStephen Lawrence <stephen.lawrence@renesas.com>2017-04-21 14:07:11 +0100
committerRonan Le Martret <ronan.lemartret@iot.bzh>2017-09-13 15:40:30 +0200
commit9f5581d2d4e644ab25c83269c8549d98af14ffc5 (patch)
treee29df7bc821fcdb9fa2b53c8061e84318c1446de /meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend
parentf16dbb642b391ded5d4d436171d2e9a09b4e9d86 (diff)
libgcc: fix bitbake QA issue "No GNU_HASH"
Yocto 2.2 changed the default linker hash style [1] which can result in "No GNU_HASH in the elf binary" QA issues during a build. This occurs building libgcc using the meta-linaro toolchain. There seems to be no upstream fix for this. As a first step disable the warning for ldflags. [1] http://www.yoctoproject.org/docs/2.2.1/ref-manual/ref-manual.html#migration-2.2-default-linker-hash-style-changed (cherry picked from commit 64c345992217b65141ca9dc1c39ca086ec50190b) Signed-off-by: Stephen Lawrence <stephen.lawrence@renesas.com>
Diffstat (limited to 'meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend')
-rw-r--r--meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend b/meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend
new file mode 100644
index 0000000..cec33a6
--- /dev/null
+++ b/meta-rcar-gen3/recipes-devtools/gcc/libgcc_%.bbappend
@@ -0,0 +1 @@
+INSANE_SKIP_${PN} = "ldflags"