summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2011-07-28 22:18:28 +0000
committerKhem Raj <raj.khem@gmail.com>2011-07-28 10:16:39 -0700
commit6c43ca6fc6a7fffc84cf28684cac0c0eb4129902 (patch)
tree5d0047210d50e7220c2a0aa97e4862464fb79b84
parent1fe892ab6876c405599c79657221a8b4675b6ecf (diff)
downloadopenembedded-core-contrib-6c43ca6fc6a7fffc84cf28684cac0c0eb4129902.tar.gz
openembedded-core-contrib-6c43ca6fc6a7fffc84cf28684cac0c0eb4129902.tar.bz2
openembedded-core-contrib-6c43ca6fc6a7fffc84cf28684cac0c0eb4129902.zip
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). 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>
-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 = ""
TUNE_ARCH ??= "INVALID"
TUNE_CCARGS ??= ""
TUNE_FEATURES ??= "${TUNE_FEATURES_tune-${DEFAULTTUNE}}"
-PACKAGE_EXTRA_ARCHS_tune-${DEFAULTTUNE} ??= "${TARGET_ARCH}"
LIBCEXTENSION ??= ""
ABIEXTENSION ??= ""