Bug 523 - Incorrect MACHINE= setting should be detected early
Summary: Incorrect MACHINE= setting should be detected early
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: All Multiple
: Medium normal
Target Milestone: 1.0 M1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-11-05 12:04 UTC by Alex deVries
Modified: 2011-02-01 10:05 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex deVries 2010-11-05 12:04:47 UTC
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.
Comment 1 Ke Yu 2010-11-06 02:59:48 UTC
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?
Comment 2 Richard Purdie 2011-02-01 10:05:04 UTC
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?