public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: "Sun, Yi" <yi.sun@intel.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Build Failed for RISC-V Image Using isar/kas-container
Date: Sun, 13 Apr 2025 10:41:57 +0300	[thread overview]
Message-ID: <98d8f6b7d0adc673ec0e2748b676588b3c86b999.camel@ilbers.de> (raw)
In-Reply-To: <BL3PR11MB6363A0B1AF096C7A2BC1014D99B02@BL3PR11MB6363.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]

On Sun, 2025-04-13 at 06:38 +0000, Sun, Yi wrote:
> 
> 
> 
> Hi All,
>  
> I'm new to ISAR and was told it's an efficient project for building
> embedded OS images.
> I'm currently trying to create an Ubuntu Noble (24.04) image for the
> RISC-V architecture.
>  
> I gave it a quick try, but ran into some issues:
> Step 1: KAS_ALLOW_ROOT=yes ./kas/kas-container menu
> Step 2: KAS_ALLOW_ROOT=yes ./kas/kas-container build (or use the
> "Build" option from the menu)
>  
> I've attached my configuration files (generated by kas-container)
> along with the error log dumped by ISAR during the build process.
>  
> Another question I have is about the concepts of "target" and "host".
> After reading as much documentation on ISAR as I could find, I'm
> still a bit confused:
>  
> Why do we need a "host" rootfs/distro, given that ISAR runs inside
> the kas-isar Docker container, which I assume already acts as the
> host environment?
> What I’m aiming for with this project is to generate an image that
> can be run in QEMU or flashed to a disk — that would be the target
> distro, right?
>  
> Any guidance or suggestions would be greatly appreciated!
>  
> Thanks
>    --Sun, Yi
> 

Hello.

Currently we support (and test) only amd64/i386 and arm64/armhf
architectures for Ubuntu despite of the fact ubuntu has ports for
riscv64 ( http://ports.ubuntu.com/ubuntu-ports/dists/noble/ ).

For now, you could try attached patch for Isar to run ubuntu-noble
build for riscv64.

Also, you need to apply patches for u-boot and kernel from 
https://patchwork.isar-build.org/project/isar/list/?series=1551 - or
wait 2..3 days until they are merged to 'next' branch.

---

In general, we might need to add other architectures supported in
ubuntu-ports into our configs. Stay tuned.

>  
> -- 
> 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/BL3PR11MB6363A0B1AF096C7A2BC1014D99B02%40BL3PR11MB6363.namprd11.prod.outlook.com
> .

-- 
Best regards,
Uladzimir.

-- 
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/98d8f6b7d0adc673ec0e2748b676588b3c86b999.camel%40ilbers.de.

[-- Attachment #2: ubuntu-riscv64.patch --]
[-- Type: text/x-patch, Size: 2557 bytes --]

diff --git a/meta-isar/conf/distro/ubuntu-common.inc b/meta-isar/conf/distro/ubuntu-common.inc
index 88a3b4f0..25aa13ea 100644
--- a/meta-isar/conf/distro/ubuntu-common.inc
+++ b/meta-isar/conf/distro/ubuntu-common.inc
@@ -12,6 +12,9 @@ HOST_BASE_DISTRO = "${BASE_DISTRO}"
 DISTRO_APT_SOURCES:arm64 ?= "conf/distro/${BASE_DISTRO}-${BASE_DISTRO_CODENAME}-ports.list"
 HOST_DISTRO_APT_SOURCES:arm64 ?= "conf/distro/${HOST_DISTRO}.list conf/distro/${HOST_DISTRO}-ports.list"
 
+DISTRO_APT_SOURCES:riscv64 ?= "conf/distro/${BASE_DISTRO}-${BASE_DISTRO_CODENAME}-ports.list"
+HOST_DISTRO_APT_SOURCES:riscv64 ?= "conf/distro/${HOST_DISTRO}.list conf/distro/${HOST_DISTRO}-ports.list"
+
 BOOTSTRAP_KEY = "file://${LAYERDIR_isar}/conf/distro/ubuntu.public.key;sha256sum=36a38199a4bf4eae1e7f574891f7dfcb79b91b87a33a499383265e1224b5e989"
 DISTRO_BOOTSTRAP_KEYS += "${BOOTSTRAP_KEY}"
 HOST_DISTRO_BOOTSTRAP_KEYS += "${BOOTSTRAP_KEY}"
diff --git a/meta-isar/conf/distro/ubuntu-noble-ports.list b/meta-isar/conf/distro/ubuntu-noble-ports.list
index adeb2639..9b101e3d 100644
--- a/meta-isar/conf/distro/ubuntu-noble-ports.list
+++ b/meta-isar/conf/distro/ubuntu-noble-ports.list
@@ -1,6 +1,6 @@
-deb	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble main restricted universe multiverse
-deb-src	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble main restricted universe multiverse
-deb	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe multiverse
-deb-src	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe multiverse
-deb	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble-security main restricted universe multiverse
-deb-src	[arch=armhf,arm64] http://ports.ubuntu.com/ubuntu-ports noble-security main restricted universe multiverse
+deb	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble main restricted universe multiverse
+deb-src	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble main restricted universe multiverse
+deb	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe multiverse
+deb-src	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe multiverse
+deb	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble-security main restricted universe multiverse
+deb-src	[arch=armhf,arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports noble-security main restricted universe multiverse

  reply	other threads:[~2025-04-13  7:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-13  6:38 Sun, Yi
2025-04-13  7:41 ` Uladzimir Bely [this message]
2025-04-13  8:02   ` Sun, Yi
2025-04-13  8:18     ` Uladzimir Bely
2025-04-13  9:58       ` Sun, Yi
2025-04-13 14:41         ` Uladzimir Bely
2025-04-14 11:48           ` Sun, Yi
2025-04-14 15:53             ` Baurzhan Ismagulov
2025-04-15  0:10               ` Sun, Yi
2025-04-15  0:33                 ` Sun, Yi
2025-04-16 19:53                   ` Uladzimir Bely
2025-04-17  0:19                     ` Sun, Yi
2025-04-16 15:42             ` Sun, Yi
2025-04-17  5:58               ` Uladzimir Bely
2025-04-17 12:08                 ` Sun, Yi
2025-04-17 15:04                   ` Uladzimir Bely
2025-04-22 13:14                 ` Sun, Yi
2025-04-22 13:56                   ` Uladzimir Bely
2025-04-22 15:34                     ` Sun, Yi
2025-04-27  9:13                       ` Sun, Yi
2025-04-27 11:32                         ` Sun, Yi
2025-04-28  7:24                           ` Baurzhan Ismagulov
2025-04-30  5:10                             ` Sun, Yi

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=98d8f6b7d0adc673ec0e2748b676588b3c86b999.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=yi.sun@intel.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