diff options
| author | Jose Quaresma <quaresma.jose@gmail.com> | 2022-06-14 17:24:38 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-06-22 23:46:29 +0100 |
| commit | 9cfff7329a060e109fdb49fdfed133fd9d291e04 (patch) | |
| tree | 63b2ecfa33b62817ce64a3a066762f9e497ec742 /meta/recipes-devtools/python/python3/0001-Avoid-shebang-overflow-on-python-config.py.patch | |
| parent | 7139d8d63b8f0311d983b6dee161bee86252efec (diff) | |
| download | poky-9cfff7329a060e109fdb49fdfed133fd9d291e04.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: 6fa49ffcf2d77aaae5c348b6eb1f0117aa93eeaf)
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>
(cherry picked from commit 5abe497aad39a6ce8d72556fcdda1938a0f8c1bc)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3/0001-Avoid-shebang-overflow-on-python-config.py.patch')
0 files changed, 0 insertions, 0 deletions