This dependency causes binutils to get rebuilt for some of our parts that are the same TARGET_ARCH but different MACHINE.
Signed-off-by: Matthew McClintock <[email protected]> --- Comments on this? It seems like it might be better to some do this in the actual recipes (binutils, gcc-cross, etc) and not globally. However, I'm not really sure what goes in MACHINEOVERIDES in general and if it could be something that would cause sstate-cache to be invalid althogh I could image some scenarios. meta/conf/bitbake.conf | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index b4335c9..48ae458 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -659,6 +659,7 @@ AUTO_LIBNAME_PKGS = "${PACKAGES}" OVERRIDES = "${TARGET_OS}:${TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:forcevariable" DISTROOVERRIDES ?= "${DISTRO}" MACHINEOVERRIDES ?= "${MACHINE}" +MACHINEOVERRIDES[vardepsexclude] += "MACHINE" CPU_FEATURES ?= "" CPU_FEATURES_arm ?= "vfp" -- 1.7.6.1 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
