summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/rsync
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-18 13:55:08 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-18 17:08:04 +0000
commit7935ae2e805d935f0f7f38e06e5ef94482540041 (patch)
tree7cd89695fa524d3fae35d56d2138fcd82bd763f5 /meta/recipes-devtools/rsync
parent88f01667707bd00b5f918950075e2235b3440b4b (diff)
downloadpoky-7935ae2e805d935f0f7f38e06e5ef94482540041.tar.gz
sstate/gcc: Fix shared workdir handling for siginfo files
For a shared workdir, any one of the fetch/unpack/patch tasks may run yet the PN and architecture fields in SSTATE_PKGSPEC may differ. This makes looking up the appropriate siginfo file near impossible. I've tried several different ways of resolving this and this is the neatest solution I could find, its still rather ugly. I believe the usefulness of better sstate debugging outweighs the ugliness of the code. This patch also changes the sstate_checkhashes() code to look for siginfo files rather than the actual sstate packages themselves. This means the function can be used in other contexts to find info files for tasks that may not have sstate data. It is assumed that sstate mirrors will have both files available. This is done to allow bitbake to query whether tasks have matching signatures in sstate directories or not. (From OE-Core rev: 068e4289b597699cbff2dfde44ba833af4535281) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/rsync')
0 files changed, 0 insertions, 0 deletions