From: Anton Mikanovich <amikan@ilbers.de>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH] install crossbuild-essential into base schroot
Date: Wed, 10 Aug 2022 17:45:16 +0300 [thread overview]
Message-ID: <d2fafa97-7f7a-93c1-dbfe-b4fb5a45bc85@ilbers.de> (raw)
In-Reply-To: <AM9PR10MB486940FDA5D734849B056B4B899F9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
04.08.2022 10:56, Moessbauer, Felix wrote:
> The CI did not report any issues with this patch, but maybe an riscv64 test is missing...
> Either we exclude these community-ports of Debian, or we simply just apply the patches for the architectures we support and we know it works (like armhf, arm64).
>
> Even if this is just a performance thing, in layers with dozens of packages the overhead of just installing the compilers is huge.
> It also bloats the upper-dir of the schroot leading to significant disk consumption.
>
> Jan recently reported that the build time raised a lot when switching an arm64 layer to from ISAR v0.9 to ISAR-next (sbuild).
> Very likely most of that came from the crossbuild-essential packages.
>
> Felix
Hello Felix,
I've just checked mc:qemuriscv64-sid-ports:isar-image-base target
manually and
it fails with:
| E: Unable to locate package crossbuild-essential-riscv64
on do_rootfs_install task of sbuild-chroot-host recipe, which was
predictable.
It was not failed on CI because of KFAIL on Sid-Ports targets (they are not
stable enough).
Overall preinstalling is good idea and will improve building speed, but we
should implement it in the right way.
[-- Attachment #2: Type: text/html, Size: 1956 bytes --]
prev parent reply other threads:[~2022-08-10 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:44 Felix Moessbauer
2022-08-04 6:07 ` Jan Kiszka
2022-08-04 6:22 ` Uladzimir Bely
2022-08-04 7:17 ` Moessbauer, Felix
2022-08-04 7:40 ` Jan Kiszka
2022-08-04 7:35 ` Anton Mikanovich
2022-08-04 7:56 ` Moessbauer, Felix
2022-08-04 8:09 ` Uladzimir Bely
2022-08-10 14:45 ` Anton Mikanovich [this message]
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=d2fafa97-7f7a-93c1-dbfe-b4fb5a45bc85@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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