summaryrefslogtreecommitdiff
path: root/meta/classes/ccache.bbclass
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-09-25 11:13:32 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-09-29 12:09:35 +0100
commit4b503f25f1ef8f554d3c76d88399db379dc818cc (patch)
treee689427f50cc19c24e267e8993e1d95fa7accf77 /meta/classes/ccache.bbclass
parente6c6d3fcfd2faf867e8145d25c1ba197fb9ee6b5 (diff)
downloadopenembedded-core-4b503f25f1ef8f554d3c76d88399db379dc818cc.tar.gz
openembedded-core-4b503f25f1ef8f554d3c76d88399db379dc818cc.tar.bz2
openembedded-core-4b503f25f1ef8f554d3c76d88399db379dc818cc.zip
sstate: Change overlapping files warning to a fatal error
When files overlap in the sysroot, something bad usually happened. We've had two independent cases recently where a couple of months after one of these warnings was shown, builds failed due to corruption. This change moves the warning to become a fatal error. The complaint I've had about this is that we need to tell the user what happened and more importantly how to recover from it. If we could recover from it, great but the trouble is we simply don't know what happened. As a compromise, we can document several of the possible scenarios in the error message. We don't normally go to this level of detail however in this case, I'm lacking other viable alternatives. I do believe it is important to stop as corruption occurs rather than letting the build contunue into territory that is not deterministic amongst other things. The complex message is followed by a simpler one in case the long message is too much for the user. (From OE-Core rev: 179ac7de03977b6e440409eddb2166819e07286a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/ccache.bbclass')
0 files changed, 0 insertions, 0 deletions