public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: benbrenson89@googlemail.com, isar-users <isar-users@googlegroups.com>
Subject: Re: multi MACHINE build for same DISTRO_ARCH
Date: Wed, 10 Jul 2019 21:09:21 +0200	[thread overview]
Message-ID: <fa0dfcf5-dcaf-bd5b-3c28-4c4d94302762@siemens.com> (raw)
In-Reply-To: <d4d70164-8683-4db8-85d3-88b269825ac2@googlegroups.com>

On 10.07.19 20:52, benbrenson89 via isar-users wrote:
>> Where does it fail?
> It fails on different points within the build. In my custom layer configuration
> it fails when building the u-boot-script recipe.
> 
> IMHO the problem appears due to running those recipes in parallel (for each
> multiconfig) and  some races appear
> when mounting/unmounting the WORKDIR into the rootfs.
> 

Vanilla u-boot-script is only built once per target arch. All normal specifics
are in the u-boot env. Or in /etc/default/u-boot-script that can be adjusted by
a machine-specific customization package. If you do the adjustment via
u-boot-script directly, you need to make that package in your overlay
machine-specific:

PN .= "-${MACHINE}"

> The next problem may appear if created packages of one MACHINE will overwritten
> by the same package of another MACHINE.
> Packages must contain a machine specific suffix in order to fix that.
> 

See above if you are deviating from the default.

Again, please study jailhouse-images carefully. It contains working pattern and
- to my best knowledge - has no multiconfig issues.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-07-10 19:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 14:41 Benedikt Niedermayr
2019-07-01 14:51 ` Jan Kiszka
2019-07-01 17:03   ` Benedikt Niedermayr
2019-07-02 10:21 ` Henning Schild
2019-07-05 16:12 ` Baurzhan Ismagulov
2019-07-10 18:52   ` benbrenson89
2019-07-10 19:09     ` Jan Kiszka [this message]
2019-07-11 17:09       ` Henning Schild

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=fa0dfcf5-dcaf-bd5b-3c28-4c4d94302762@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=benbrenson89@googlemail.com \
    --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