Bug 6563 - bitbake-memres does not create bitbake.lock
Summary: bitbake-memres does not create bitbake.lock
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.7 M4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-07-21 12:48 UTC by Stoicescu Cornel
Modified: 2014-09-23 19:25 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2014-07-21 12:48:48 UTC
Found on poky master:231c7373fb760d777cd29d27129c68374968cbff

Steps to reproduce:

1) get poky sources (see above commit)
NOTE: The poky source should not have an already-made 'build' directory within
2) in a fresh shell session, source oe-init-build-env-memres
3) issue 'bitbake core-image-minimal'

Notice error:
Failed to read bitbake.lock ([Errno 2] No such file or directory: './bitbake.lock'), invalid port

Expected result:
As per source command output:
### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    adt-installer
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
Bitbake server started on demand as needed, use bitbake -m to shut it down