summaryrefslogtreecommitdiffstats
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:45 +0000
commit464a4f628f4ec20e2220312e0caa40019edf58ad (patch)
tree9fae3f45c7edfb664c4e35175cff0d8b13f96af6
parentf2f2fa61e2c331409f20c999f93d78ef752b4fd2 (diff)
downloadopenembedded-core-contrib-464a4f628f4ec20e2220312e0caa40019edf58ad.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] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-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 += " \
"
SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \
- gcc-cross-${TARGET_ARCH}->virtual/libc \
+ gcc-cross-${TARGET_ARCH}->virtual/${TARGET_PREFIX}libc-for-gcc \
gcc-cross-${TARGET_ARCH}->linux-libc-headers \
ppp-dialin->ppp \
resolvconf->bash \