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 <[email protected]> --- meta/conf/bitbake.conf | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 6e109ec..9c80f11 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 ??= "" -- 1.7.4.1 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
