summaryrefslogtreecommitdiffstats
path: root/meta/conf
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-11-16 09:08:28 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-11-16 13:30:50 +0000
commit2cb1aee04840e9ed7dc4a4952e8d883eda1feb90 (patch)
tree98c85ab1375eb91352e1f1f87c3a4a3d1ad53413 /meta/conf
parent88f9310ce0015be539ffefbeff4b64c73779fdc9 (diff)
downloadpoky-2cb1aee04840e9ed7dc4a4952e8d883eda1feb90.tar.gz
layer.conf: Correct gcc-cross dependency
The dependency listed in layer.conf is incorrect, gcc-cross DEPENDS on ${TARGET_PREFIX}libc-for-gcc, not virtual/libc. These happen to resolve the same values however they may not always both be built. The result of this was that gcc-cross gets a different task hash depending on whether virtual/libc was included in the build. Specifically "bitbake m4" and "bitbake virtual/kernel" would result in different task checksums. The fix is to use the correct dependency name. [YOCTO #8692] (From OE-Core rev: 464a4f628f4ec20e2220312e0caa40019edf58ad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf')
-rw-r--r--meta/conf/layer.conf2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index 2ecba0f937..3569b09d95 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -41,7 +41,7 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \
41" 41"
42 42
43SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \ 43SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \
44 gcc-cross-${TARGET_ARCH}->virtual/libc \ 44 gcc-cross-${TARGET_ARCH}->virtual/${TARGET_PREFIX}libc-for-gcc \
45 gcc-cross-${TARGET_ARCH}->linux-libc-headers \ 45 gcc-cross-${TARGET_ARCH}->linux-libc-headers \
46 ppp-dialin->ppp \ 46 ppp-dialin->ppp \
47 resolvconf->bash \ 47 resolvconf->bash \