From: Jan Kiszka <jan.kiszka@siemens.com>
To: benbrenson89@googlemail.com, isar-users <isar-users@googlegroups.com>
Subject: Re: Bug mcopy (wic) when creating bootpartition
Date: Thu, 27 Feb 2020 10:42:13 +0100 [thread overview]
Message-ID: <809cd26c-9cca-3647-59be-d0f2c2f71020@siemens.com> (raw)
In-Reply-To: <9a605191-9af0-41d6-a414-75970acac66c@googlegroups.com>
On 27.02.20 10:32, benbrenson89 via isar-users 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?
> 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?
Running always in the target environment reduces variations because we
have to do that anyway when cross-compiling is disabled (which is
default and recommended for production build).
Can you extract the problem to something that can be tested separately?
What is your target architecture? What is the qemu-user-static version
you are effectively using?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-02-27 9:42 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 [this message]
2020-02-27 12:33 ` benbrenson89
2020-02-27 16:10 ` Jan Kiszka
2020-03-09 17:04 ` 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=809cd26c-9cca-3647-59be-d0f2c2f71020@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