Bug 7935

Summary:	Bitbake relies on absolute path for TMPDIR
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Igor Stoppa <igor.stoppa>
Component:	bitbake	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	poky.bs.watcher, poky.watcher
Version:	unspecified
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Igor Stoppa 2015-06-30 13:11:15 UTC

Preconditions/Environment
-------------------------
I had a project in /home/user/myproject
From there, as usual, I run ". ./oe-init-build-env"
then "bitbake target" went fine


Triggering Action/Cause
-----------------------
mv /home/user/myproject /home/user/_myproject
cd /home/user/_myproject
. ./oe-init-build-env
bitbake -c cleanall target

Expectation
-----------
The target should be cleaned.

Actual Result
-------------
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:

Error, TMPDIR has changed location. You need to either move it back to 
/home/user/myproject/build/tmp-glibc or rebuild

--
The relative path of the temporary directory has not changed, it is still in the same location, referring to the root of the project.
bitbake should not force me to either rebuild or disable a safety check for something that is completely safe.



Reproducibility
---------------
2/2

But this seems to be systematic.


Reverting the moved project ot its initial location makes the error message disappear.

Comment 1 Richard Purdie 2015-07-02 14:48:19 UTC

The system does not support moving TMPDIR around for a variety of long and boring reasons. If you do need to move TMPDIR, you'd rebuild from an sstate directory instead in a new TMPDIR, then the relocation code is triggered correctly.