Bug 5293

Summary:	local.conf is not reloaded when using bitbake background server
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Stoicescu Cornel <corneliux.stoicescu>
Component:	bitbake	Assignee:	Cristiana Voicu <cristiana.voicu>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, sgw
Version:	1.5
Target Milestone:	1.5.1
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Stoicescu Cornel 2013-09-30 12:44:01 UTC

1) get poky sources (1.5 +)
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) in conf/local.conf modify BB_NUMBER_THREADS and PARALLEL_MAKE to be different than 1
4) in conf/local.conf, change MACHINE to qemux86-64
5) issue 'bitbake core-image-minimal'

-notice bitbake is using only 1 thread
-notice image built is for qemux86

I believe that local.conf is not interpreted.

Comment 1 Richard Purdie 2013-09-30 21:29:59 UTC

This sounds like a cache validation bug, the file is used but it doesn't reload the file when it has changed.

Comment 2 Cristiana Voicu 2013-11-25 14:36:45 UTC

#5535 treats the same issue

*** This bug has been marked as a duplicate of bug 5535 ***