From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/4] 32-bit compat arch support
Date: Mon, 21 Sep 2020 11:41:44 +0200 [thread overview]
Message-ID: <20200921094144.GM16317@yssyq.m.ilbers.de> (raw)
In-Reply-To: <5543a66d-16ce-1606-162b-f55ef7a0c4c1@siemens.com>
On Mon, Sep 21, 2020 at 11:24:51AM +0200, Jan Kiszka wrote:
> Any feedback on this? We are about to move this into production, exposing it
> to end-users.
Thanks for the info, will have a more detailed look and let you know.
Regarding "qemuarm-stretch" stuff: Those reference verbatim file names under
meta-isar/conf/multiconfig. Just cutting the "qemu" part is confusing as well,
as the remaining part isn't how it's called in Debian.
I've re-read the preceding paragraph, literally it doesn't imply only qemu
stuff is cross-buildable; but I see what you mean. The obvious options are 1.
to mention non-qemu configurations in the list and 2. rewrite the entries using
Debian arch names ("stretch armhf", etc.).
But let me ask the other way round, are there configurations in stock Isar that
don't support cross-building? Do we need to document the ones that do so
explicitly?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-09-21 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:13 Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 1/4] Add compat architecture support via multiarch Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 2/4] ci: Add compat arch support Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 3/4] doc: Enhance list of supported cross-archs, drop QEMU reference Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 4/4] doc: Describe new compat arch support Jan Kiszka
2020-09-21 9:24 ` [PATCH v2 0/4] 32-bit " Jan Kiszka
2020-09-21 9:41 ` Baurzhan Ismagulov [this message]
2020-09-21 12: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=20200921094144.GM16317@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