| Summary: |
bitbake-memres does not create bitbake.lock |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
Stoicescu Cornel <corneliux.stoicescu> |
| Component: |
bitbake | Assignee: |
Richard Purdie <richard.purdie> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
poky.bs.watcher, poky.watcher
|
| Version: |
1.7 | |
|
| Target Milestone: |
1.7 M4 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
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