From: Henning Schild <henning.schild@siemens.com>
To: benbrenson89 via isar-users <isar-users@googlegroups.com>
Cc: <benbrenson89@googlemail.com>
Subject: Re: Bug mcopy (wic) when creating bootpartition
Date: Mon, 9 Mar 2020 18:04:43 +0100 [thread overview]
Message-ID: <20200309180443.687849ff@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <9a605191-9af0-41d6-a414-75970acac66c@googlegroups.com>
On Thu, 27 Feb 2020 01:32:31 -0800
benbrenson89 via isar-users <isar-users@googlegroups.com> wrote:
> Hi guys,
>
> I have encountered a bug related to mcopy during wic image generation.
>
> I digged a bit deeper into the problem and it turns out that mcopy is
> not able to copy folders recursive. It just silently skips the
> content of those folders.
>
> When running mcopy within the buildchroot-host, these folders where
> properly copied.
>
> My question now:
>
> Wic is running in the buildchroot of the target architecture, but I
> don't get why it has to be done in there?
Back in the early days of wic we ran it on the host. But that had
really nasty side-effects that are simply not acceptable. It needs to
run in the "same debian" that you want to build for. i.e. so you get
the bootloader binaries of the bootloader you expect
> May it be possible to switch the wic image generation into the
> host-buildchroot, or are there any other requirements for the current
> environment which I miss here?
A host-buildchroot would probably work as well. But i doubt it would
solve your problem. But it can not be the default since cross is an
experimental feature that we do not suggest for production. But it
works well to speed up dev builds.
Henning
>
> Greets Benedikt
>
prev parent reply other threads:[~2020-03-09 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 9:32 benbrenson89
2020-02-27 9:42 ` Jan Kiszka
2020-02-27 12:33 ` benbrenson89
2020-02-27 16:10 ` Jan Kiszka
2020-03-09 17:04 ` Henning Schild [this message]
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=20200309180443.687849ff@md1za8fc.ad001.siemens.net \
--to=henning.schild@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