public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/2] Fix u-boot-script packages conflict
Date: Fri, 14 Jan 2022 16:57:08 +0300	[thread overview]
Message-ID: <20220114135710.72647-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}.
Now we can depend on any kernel and make u-boot-script packages equal.

Anton Mikanovich (2):
  dpkg: Introduce any kernel variables
  u-boot-script: Depend on any kernel package

 meta/classes/dpkg-base.bbclass                      | 7 +++++++
 meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb | 2 +-
 meta/recipes-kernel/linux/files/debian/control.tmpl | 2 ++
 3 files changed, 10 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2022-01-14 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 13:57 Anton Mikanovich [this message]
2022-01-14 13:57 ` [PATCH v2 1/2] dpkg: Introduce any kernel variables Anton Mikanovich
2022-01-14 16:40   ` Jan Kiszka
2022-01-14 13:57 ` [PATCH v2 2/2] u-boot-script: Depend on any kernel package Anton Mikanovich
2022-01-14 16:40   ` Jan Kiszka
2022-01-14 17:23     ` Jan Kiszka
2022-01-15  9:57       ` Anton Mikanovich

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=20220114135710.72647-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