summaryrefslogtreecommitdiffstats
path: root/meta
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-11 13:20:20 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-18 12:13:43 +0100
commit2d89cff42af2bb0049224bfaaebaa2b21966169f (patch)
tree83b19d4c8d1afd881bd4273d54853449595d5073 /meta
parenteb8a8fe503de277eb1b5c6b4c157368b2bee116e (diff)
downloadpoky-2d89cff42af2bb0049224bfaaebaa2b21966169f.tar.gz
sstate: Use -m option to tar when unpacking sstate
We've noticed failures on the project autobuilders where a shared sstate directory is used across multiple builders and the clocks become skewed. Most of the time this causes harmless building but if this happens where an environment is changed (make install vs make in qt4-x11-free for example), the build can fail. This avoids modification times in the future and should make builds safer in shared environments sstate was designed for. (From OE-Core rev: 8f1bdb4f4afd7f5f4c121be8ba82f4675f73e300) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta')
-rw-r--r--meta/classes/sstate.bbclass2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 3fcaa659ea..b60c766093 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -544,7 +544,7 @@ sstate_create_package () {
544sstate_unpack_package () { 544sstate_unpack_package () {
545 mkdir -p ${SSTATE_INSTDIR} 545 mkdir -p ${SSTATE_INSTDIR}
546 cd ${SSTATE_INSTDIR} 546 cd ${SSTATE_INSTDIR}
547 tar -xvzf ${SSTATE_PKG} 547 tar -xmvzf ${SSTATE_PKG}
548} 548}
549 549
550# Need to inject information about classes not in the global configuration scope 550# Need to inject information about classes not in the global configuration scope