From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Hirotaka Motai <hirotaka.motai@miraclelinux.com>,
isar-users@googlegroups.com
Subject: Re: Question: How to build ARM32 rootfs with ARM64 Kernel
Date: Fri, 26 Dec 2025 11:59:24 +0100 [thread overview]
Message-ID: <28a92f28-e2ed-4607-b60b-3ce9a0260144@web.de> (raw)
In-Reply-To: <CANqL_VJzcnSbfEW9Sb0LUBfoOep027J4Vxg4MRpqOV9VEQZT9A@mail.gmail.com>
Hi Matai-san,
On 25.12.25 09:18, Hirotaka Motai wrote:
> Hi Isar team,
>
> I am currently considering using ISAR to build a system with the
> following architecture:
>
> * Kernel: ARM64 (64-bit)
> * rootfs: ARM32 (32-bit)
>
> I understand that the ISAR_ENABLE_COMPAT_ARCH option allows for the
> building of
> some 32-bit packages, but in this case, I want to build all packages as
> 32-bit.
>
> Could you please let me know if this somewhat special configuration of
> "32-bit rootfs
> with 64-bit kernel" is supported for cross-architecture building within
> ISAR?
> If it is possible, I would greatly appreciate it if you could provide
> the specific steps,
> such as the necessary settings in local.conf.
>
Not a completely simple question, indeed. The rootfs arch is defined by
DISTRO_ARCH. But that one also influences the arch that the custom
kernel will select. You could try a multiconfig build, setting
DISTRO_ARCH to arm64 only for the kernel part and then requesting the
arm64 kernel from your armhf rootfs. Or you try to set KERNEL_ARCH
explicitly in the custom kernel recipe, switching it from "arm" (as
armhf would defined it) to "arm64". The former may give more correct
results, though, because the kernel recipe will still use DISTRO_ARCH
with "armhf" for a arm64 kernel.
Jan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/28a92f28-e2ed-4607-b60b-3ce9a0260144%40web.de.
next prev parent reply other threads:[~2025-12-26 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 8:18 Hirotaka Motai
2025-12-25 10:17 ` Baurzhan Ismagulov
2025-12-26 10:59 ` 'Jan Kiszka' via isar-users [this message]
2026-01-06 2:43 ` Hirotaka Motai
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=28a92f28-e2ed-4607-b60b-3ce9a0260144@web.de \
--to=isar-users@googlegroups.com \
--cc=hirotaka.motai@miraclelinux.com \
--cc=jan.kiszka@web.de \
/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