From: "Sun, Yi" <yi.sun@intel.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Build Failed for RISC-V Image Using isar/kas-container
Date: Tue, 22 Apr 2025 21:14:56 +0800 [thread overview]
Message-ID: <aAeWUO3tTH3m1Z2M@ysun46-mobl.ccr.corp.intel.com> (raw)
In-Reply-To: <6d0886ebe7e6479d50ffb5678b1dba0264681e3a.camel@ilbers.de>
On 17.04.2025 08:58, Uladzimir Bely wrote:
>
>Hello.
>
>This looks like a temporary bug, when `ubuntu-ports` repo is temporary
>not synchronized with `ubuntu` one. We periodicaly face it and can't do
>anything with it.
>
>I also this issue now when crossbuilding riscv64 and arm64 ubuntu-noble
>targets. It was not reproduced week ago.
>
>There are two options to get a successfull build:
>
>1. Disable cross-compile option - but it is relatively slow.
>2. Use some snapshot that is known to work.
>
>For example, this additional configuration (I used one-week-ago
>snapshot) works for me:
>
>```
>Mirror selection
>- [*] Use the distros snapshot mirror
> - (*) Custom date
> - (20250410T000000Z) Custom snapshot date
>```
>
>I'm attaching kas configuration I can get working build with.
Hi Uladzimir,
I'm adding some actual .bb files for my project and have a few questions.
1, It seems the installation of the linux-libc-dev package is failing in the host rootfs.
Have you happened to run into this issue before?
```
| Broken libc6-dev:amd64 Depends on linux-libc-dev:amd64 < none @un pH >
| Considering linux-libc-dev:amd64 1 as a solution to libc6-dev:amd64 24
| Considering linux-libc-dev:amd64 1 as a solution to libc6-dev:amd64 24
| Done
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libc6-dev : Depends: linux-libc-dev but it is not installable
| E: Unable to correct problems, you have held broken packages.
| WARNING: exit code 100 from a shell command.
| DEBUG: Executing shell function rootfs_do_umounts
| DEBUG: Shell function rootfs_do_umounts finished
| DEBUG: Python function do_rootfs_install finished
ERROR: Task (/build/../repo/meta-isar/recipes-devtools/sbuild-chroot/sbuild-chroot-host-db2m.bb:do_rootfs_install) failed with exit code '1' ```
2, So I tried disabling cross-build working aroud above issue. As you mentioned, the performance is quite poor.
Would you mind explaining a bit more about why that happens? And is there anything I can do to improve it?
3, Do you have an estimated timeline for the v0.10 release?
Thanks
--Sun, Yi
--
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/aAeWUO3tTH3m1Z2M%40ysun46-mobl.ccr.corp.intel.com.
next prev parent reply other threads:[~2025-04-22 13:15 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
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 [this message]
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=aAeWUO3tTH3m1Z2M@ysun46-mobl.ccr.corp.intel.com \
--to=yi.sun@intel.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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