Right now, if you set in your local.conf: MACHINE=nonexistent The build spends a lot of time building the -natives, and only seems to fail when it hits linux-wrs. Somehow, this should warn you of this error earlier.
Interesting, i did not reproduce in my box. after set MACHINE=nonexist, bitbake will immediatly prompt error: # set MACHINE=nonexistent in local.conf # bitbake poky-image-sdk " FATAL: Poky's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. Please set a valid MACHINE in your local.conf " I tried both fresh build and incremental build, same result. so Alex, did i miss some specific config from your environment?
Likewise, I just tried setting an invalid MACHINE here and immediately got an error about it like Ke did. Alex, can you please advise if you're still seeing this problem?