summaryrefslogtreecommitdiffstats
path: root/meta/conf
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2011-07-28 22:18:28 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-01 14:16:54 +0100
commit50f021e270b54b47b6528e8a395d3ba56308f4c1 (patch)
tree8851c6233df1dbe0eda2bc14e037dd22507d32e1 /meta/conf
parentf94b781695cd8fa387daff16ecbf3987a0883018 (diff)
downloadpoky-50f021e270b54b47b6528e8a395d3ba56308f4c1.tar.gz
bitbake.conf: remove PACKAGE_EXTRA_ARCHS_tune-XXX default
Because of the way BitBake handles ??= under certain circumstances, this default setting ends up stepping all over the real setting from the arch include file. Since virtually all arch include files or tune files define a real value for this we shouldn't need to have a default (or it needs to be done in a different way). (From OE-Core rev: 6c43ca6fc6a7fffc84cf28684cac0c0eb4129902) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Acked-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf')
-rw-r--r--meta/conf/bitbake.conf1
1 files changed, 0 insertions, 1 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 6e109ecd1e..9c80f11085 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -84,7 +84,6 @@ HOST_EXEEXT = ""
84TUNE_ARCH ??= "INVALID" 84TUNE_ARCH ??= "INVALID"
85TUNE_CCARGS ??= "" 85TUNE_CCARGS ??= ""
86TUNE_FEATURES ??= "${TUNE_FEATURES_tune-${DEFAULTTUNE}}" 86TUNE_FEATURES ??= "${TUNE_FEATURES_tune-${DEFAULTTUNE}}"
87PACKAGE_EXTRA_ARCHS_tune-${DEFAULTTUNE} ??= "${TARGET_ARCH}"
88LIBCEXTENSION ??= "" 87LIBCEXTENSION ??= ""
89ABIEXTENSION ??= "" 88ABIEXTENSION ??= ""
90 89