From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 0/2] Fix u-boot-script packages conflict
Date: Tue, 11 Jan 2022 12:36:54 +0300 [thread overview]
Message-ID: <20220111093656.220514-1-amikan@ilbers.de> (raw)
When trying to execute do_prepare_build task of u-boot-script package
for some targets 'multiple execution' occurs:
$ bitbake mc:bananapi-buster:u-boot-script:do_prepare_build mc:de0-nano-soc-buster:u-boot-script:do_prepare_build
ERROR: Detect multiple executions of do_prepare_build in /build/tmp/work/debian-buster-armhf/u-boot-script/1.1-r0
ERROR: Rerun a clean build with empty STAMPCLEAN and compare the sigdata files
This is caused by different u-boot-script packages building in the same
directory. The difference between those two output debs is dependency on
linux-image-${KERNEL_NAME}, so we need to separate them and fix Isar to
allow parallel building.
Anton Mikanovich (2):
dpkg: Allow parallel build of different package versions
u-boot-script: Split packages by kernel
meta/classes/dpkg-base.bbclass | 7 +++++--
meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb | 3 +++
2 files changed, 8 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2022-01-11 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:36 Anton Mikanovich [this message]
2022-01-11 9:36 ` [PATCH 1/2] dpkg: Allow parallel build of different package versions Anton Mikanovich
2022-01-11 9:48 ` Henning Schild
2022-01-11 9:36 ` [PATCH 2/2] u-boot-script: Split packages by kernel Anton Mikanovich
2022-01-11 9:50 ` Henning Schild
2022-01-11 12:03 ` Jan Kiszka
2022-01-11 15:05 ` Anton Mikanovich
2022-01-11 15:56 ` Jan Kiszka
2022-01-12 13:34 ` Anton Mikanovich
2022-01-12 13:51 ` Schmidt, Adriaan
2022-01-12 13:59 ` Jan Kiszka
2022-01-12 13:58 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220111093656.220514-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox