From: Anton Mikanovich <amikan@ilbers.de>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"ibr@ilbers.de" <ibr@ilbers.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v4 1/2] run imager in buildchroot-host on cross
Date: Fri, 16 Sep 2022 10:41:10 +0300 [thread overview]
Message-ID: <8b8c3eaf-45bd-906f-bd30-4794bc2f3b8f@ilbers.de> (raw)
In-Reply-To: <AM9PR10MB486999C45AF4718B301B1B4689499@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
15.09.2022 20:08, Moessbauer, Felix wrote:
> I just checked and for me it worked without any issues.
>
> Still, nobody answered my question about the distro-arch==host-arch question, huh!
> Before sending a v5, I'll wait for a clarification.
Running amd64 targets with enabled cross compile really don't have much
sense,
but we have some logic in buildchroot.bbclass which makes Isar to use host
buildchroot in this case (and no such a logic for SDK - is that a bug?).
next prev parent reply other threads:[~2022-09-16 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 20:21 [PATCH v4 0/2] use xz and gzip on host (outside chroot) Felix Moessbauer
2022-09-14 20:21 ` [PATCH v4 1/2] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-15 9:14 ` Anton Mikanovich
2022-09-15 9:35 ` Moessbauer, Felix
2022-09-15 10:45 ` Anton Mikanovich
2022-09-15 11:04 ` Moessbauer, Felix
2022-09-15 11:06 ` Henning Schild
2022-09-15 15:43 ` Anton Mikanovich
2022-09-15 11:08 ` Henning Schild
2022-09-15 15:44 ` Anton Mikanovich
2022-09-15 17:08 ` Moessbauer, Felix
2022-09-16 7:41 ` Anton Mikanovich [this message]
2022-09-14 20:21 ` [PATCH v4 2/2] add wic.xz image to qemuarm64-bookworm Felix Moessbauer
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=8b8c3eaf-45bd-906f-bd30-4794bc2f3b8f@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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