summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/vim/vim.inc
diff options
context:
space:
mode:
authorJose Quaresma <quaresma.jose@gmail.com>2022-06-14 17:24:38 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-06-15 12:27:01 +0100
commit0b17d4493548bd4ec3c79364721be926bcaea244 (patch)
tree826ceb7ab2d4f0db490f81c764ebeec1cf837ea7 /meta/recipes-support/vim/vim.inc
parent11d5f2ce25152c1d9023c274f63038fd74314d80 (diff)
downloadpoky-0b17d4493548bd4ec3c79364721be926bcaea244.tar.gz
archiver: don't use machine variables in shared recipes
When using multiconfig with the same TMP folder we can have races because the shared recipes like gcc-source run twice. ARCHIVER_OUTDIR = ${ARCHIVER_TOPDIR}/${TARGET_SYS}/${PF}/ which includes TARGET_SYS and between the two different MACHINE values, this changes from 'arm-poky-linux-gnueabi' to 'aarch64-poky-linux'. This leads to the task running twice, once for each multiconfig. To solve this we need to store the shared output in a common place for all machines and in this way the stamps will be the same for each machine so the gcc-source will on run once regardless of the machine used. (From OE-Core rev: 5abe497aad39a6ce8d72556fcdda1938a0f8c1bc) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/vim/vim.inc')
0 files changed, 0 insertions, 0 deletions