aboutsummaryrefslogtreecommitdiffstats
path: root/meta/classes/sstate.bbclass
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:03:26 +0100
commit8f1bdb4f4afd7f5f4c121be8ba82f4675f73e300 (patch)
treee2cbc45c937d7e8ea77d8fd3791036474269e5ba /meta/classes/sstate.bbclass
parentfa9ccb23e5788f331cc868ce4bad4abd1eaeee9c (diff)
downloadopenembedded-core-8f1bdb4f4afd7f5f4c121be8ba82f4675f73e300.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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/sstate.bbclass')
-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 () {
sstate_unpack_package () {
mkdir -p ${SSTATE_INSTDIR}
cd ${SSTATE_INSTDIR}
- tar -xvzf ${SSTATE_PKG}
+ tar -xmvzf ${SSTATE_PKG}
}
# Need to inject information about classes not in the global configuration scope