From: "Sun, Yi" <yi.sun@intel.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: Baurzhan Ismagulov <ibr@radix50.net>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Build Failed for RISC-V Image Using isar/kas-container
Date: Thu, 17 Apr 2025 08:19:12 +0800 [thread overview]
Message-ID: <aABJAEMCTpPhvSft@ysun46-mobl.ccr.corp.intel.com> (raw)
In-Reply-To: <5002759cb4c7010e2668056c4fd7e5627ce98aa3.camel@ilbers.de>
On 16.04.2025 22:53, Uladzimir Bely wrote:
>On Tue, 2025-04-15 at 00:33 +0000, Sun, Yi wrote:
>> BTW, the error will not happen if run that copy command in the docker
>> manually:
>>
>> # ./kas/kas-container shell
>> root@fe0d1f3b7b5e:/build#
>> "/repo/scripts:/repo/bitbake/bin:/usr/sbin:/usr/bin:/sbin:/bin" cp -
>> fpPRH "/build/../repo/meta/recipes-devtools/isar-
>> apt/files/distributions.in" "."
>>
>> Thanks
>> --Sun, Yi
>>
>> -----Original Message-----
>> From: Sun, Yi
>> Sent: Tuesday, April 15, 2025 08:10
>> To: Baurzhan Ismagulov <ibr@radix50.net>; isar-users@googlegroups.com
>> Cc: Uladzimir Bely <ubely@ilbers.de>
>> Subject: RE: Build Failed for RISC-V Image Using isar/kas-container
>>
>> Hi Baurzhan,
>>
>> Nope, I'm trying to build it on an Ubuntu 22.04.4 LTS native machine.
>>
>> Thanks
>> --Sun, Yi
>>
>
>But probably filesystem where project is run is not something like
>ext4/btrfs, but, e.g. ntfs?
>
>In another your message you remove "-p" option of `cp` and this somehow
>helps. This definitely means that either the filesystem you are using
>doesn't support standard linux file permissions or something else (e.g.
>ACLs) doesn't allow you to do it.
I've checked my partition: one is vFAT (used for EFI), and the other two are ext4:
➜ isar git:(ubely/riscv64) ✗ blkid
/dev/nvme0n1p1: UUID="083cdf27-..." BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="37d996f0-..."
/dev/sda2: UUID="ebd1da1b-2940-..." BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e3b2e602-..."
/dev/sda1: UUID="5E71-..." BLOCK_SIZE="512" TYPE="vfat" PARTUUID="08e794af-..."
Anyway, it would be good if there was a toggle to switch 'preserve the specified attributes' for cp.
I'd also be grateful if you have some time to take a look at this new issue —
it seems to be broken by some RISC-V package during the do_bootstrap_host step.
```
The following packages have unmet dependencies:
build-essential : Depends: libc6-dev but it is not installable or
libc-dev
devscripts : Depends: gnupg but it is not installable or
gnupg2 but it is not installable
libc-dev-bin:riscv64 : Depends: libc6:riscv64 (> 2.39) but it is not installable
Depends: libc6:riscv64 (< 2.40) but it is not installable
libc6-dev:riscv64 : Depends: libc6:riscv64 (= 2.39-0ubuntu8.4) but it is not installable
libcrypt-dev:riscv64 : Depends: libcrypt1:riscv64 (= 1:4.4.36-4build1) but it is not installable
libgcc-13-dev : Breaks: libgcc-13-dev:riscv64 (!= 13.2.0-16ubuntu1) but 13.3.0-6ubuntu2~24.04 is to be installed
libgcc-13-dev:riscv64 : Depends: gcc-13-base:riscv64 (= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libgcc-s1:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libgomp1:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libitm1:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libatomic1:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libasan8:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libubsan1:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Breaks: libgcc-13-dev (!= 13.3.0-6ubuntu2~24.04) but 13.2.0-16ubuntu1 is to be installed
libstdc++-13-dev : Depends: libc6-dev (>= 2.13-0ubuntu6) but it is not installable
Breaks: libstdc++-13-dev:riscv64 (!= 13.2.0-16ubuntu1) but 13.3.0-6ubuntu2~24.04 is to be installed
libstdc++-13-dev:riscv64 : Depends: gcc-13-base:riscv64 (= 13.3.0-6ubuntu2~24.04) but it is not installable
Depends: libstdc++6:riscv64 (>= 13.3.0-6ubuntu2~24.04) but it is not installable
Breaks: libstdc++-13-dev (!= 13.3.0-6ubuntu2~24.04) but 13.2.0-16ubuntu1 is to be installed
libtool : Depends: libc6-dev but it is not installable or
libc-dev
```
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/aABJAEMCTpPhvSft%40ysun46-mobl.ccr.corp.intel.com.
next prev parent reply other threads:[~2025-04-17 0:20 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 [this message]
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=aABJAEMCTpPhvSft@ysun46-mobl.ccr.corp.intel.com \
--to=yi.sun@intel.com \
--cc=ibr@radix50.net \
--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