From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-bootstrap fails to rebuild after config changes
Date: Wed, 21 Aug 2019 11:02:09 +0200 [thread overview]
Message-ID: <20190821090209.GA31401@yssyq.m.ilbers.de> (raw)
In-Reply-To: <94e2ed05-76df-2071-9528-e3765e1b8de8@siemens.com>
On Tue, Aug 20, 2019 at 09:33:29PM +0200, Jan Kiszka wrote:
> Actually, I do not even see the point of locking here: If a bootstrap target
> is shared, only one multiconfig target will request its build and the others
> will wait automatically for the result. That's what bitbake is supposed to
> do for us. If it's not shared, there is no conflict to use locks on. We only
> need locks if different tasks of different recipes compete for common
> resources.
There were build issues. Maybe that is the case when the host and the target
arch are the same. We might be able to reproduce that by trying to build
2c99c8d.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-21 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 17:18 Jan Kiszka
2019-08-13 8:01 ` Claudius Heine
2019-08-13 8:14 ` Jan Kiszka
2019-08-20 19:33 ` Jan Kiszka
2019-08-21 9:02 ` Baurzhan Ismagulov [this message]
2019-08-21 9:06 ` 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=20190821090209.GA31401@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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