Bug 2071 - Running bitbake from a subdir issues unhelpful sanity error
Summary: Running bitbake from a subdir issues unhelpful sanity error
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.2
Hardware: All Multiple
: Low minor
Target Milestone: 1.2 M4
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard: Patch merged to master (14 Mar)
Depends on:
Blocks:
 
Reported: 2012-03-10 01:24 UTC by Darren Hart
Modified: 2012-03-14 23:32 UTC (History)
2 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 Darren Hart 2012-03-10 01:24:27 UTC
On occasion I dive into the tmp dir from my build shell, forget I did that, then issue another bitbake command without backing out to the root build dir. Bitbake issues the following warning:

ERROR:  OE-core'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 a MACHINE in your local.conf or environment
Your version of local.conf was generated from an older version of local.conf.sample and there have been updates made to this file. Please compare the two files and merge any changes before continuing.
Matching the version numbers will remove this message.
"meld conf/local.conf conf/local.conf.sample" is a good way to visualise the changes.

ERROR: Execution of event handler 'check_sanity_eventhandler' failed

It would be nicer if it said:

"ERROR: bitbake must be run from the root buildir: /build/poky/fri2"

I believe this should be a relatively easy thing to test for prior to the sanity checker discovering there isn't a MACHINE defined (b/c there is no $CWD/conf/local.conf).
Comment 1 Darren Hart 2012-03-10 01:25:03 UTC
Taking a wild guess that this is up Paul's alley. Paul, please request a re-assignment (of the bug that is) if you disagree :-)
Comment 2 Darren Hart 2012-03-10 01:26:06 UTC
Marking as 1.2 M4 as this seems like a fix consistent with the effort of reducing warnings and otherwise cleaning up the output. If you disagree, 1.3 is fine too.
Comment 3 Paul Eggleton 2012-03-14 23:32:38 UTC
Patch merged to master in revision 50e4d4c3123dff43bd4abecccae1f3ae13784e9b.