Patchwork [1/1] classes/sanity: check if SDKMACHINE setting has taken effect

mail settings
Submitter Paul Eggleton
Date March 31, 2014, 10:29 a.m.
Message ID <>
Download mbox | patch
Permalink /patch/69681/
State Accepted
Commit 25ba4042ae782016aaf1cb5d3dac09b2a1030a1e
Headers show


Paul Eggleton - March 31, 2014, 10:29 a.m.
If you try to set SDKMACHINE in a distro configuration file, it won't
take effect because by the time that is parsed the line in bitbake.conf
which includes the appropriate conf file for SDKMACHINE has already been
parsed. Check that SDK_ARCH has changed from its default value and show
an error if it hasn't in order to catch this misconfiguration.

Fixes [YOCTO #5861].

Signed-off-by: Paul Eggleton <>
 meta/classes/sanity.bbclass | 2 ++
 1 file changed, 2 insertions(+)


diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index cf514d0..69d6a24 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -667,6 +667,8 @@  def check_sanity_everybuild(status, d):
     if d.getVar('SDKMACHINE', True):
         if not check_conf_exists("conf/machine-sdk/${SDKMACHINE}.conf", d):
             status.addresult('Specified SDKMACHINE value is not valid\n')
+        elif d.getVar('SDK_ARCH', False) == "${BUILD_ARCH}":
+            status.addresult('SDKMACHINE is set, but SDK_ARCH has not been changed as a result - SDKMACHINE may have been set too late (e.g. in the distro configuration)\n')