From: roberto.foglietta@gmail.com
To: isar-users@googlegroups.com
Cc: roberto.foglietta@gmail.com
Subject: [PATCH] Rebuild after cleaning does not work anymore, bugfix
Date: Tue, 06 Dec 2022 23:06:43 +0000 [thread overview]
Message-ID: <4uil9nq8jkub.6oVt5dOuml8uqWJ9Z3m4rw2@16F0H.trk.elasticemail.com> (raw)
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
bugfix, image and roofs classes, fails in rebuilding - rebuild after cleaning
does not work anymore but it is required to remove manually all the directories
and this would take longer to rebuild. This patch fixes this new worng
behaviour which happens when the kernel is not compile but installed.
Reproducibility: this sequence of commands does not work anymore
kcbuild
./kas-container --isar clean
XOR/AND
sudo ./kas-container clean
kcbuild
It fails with error while the following still works
kcbuild
sudo rm -rf build/tmp build/sstate-cache
kcbuild
but it takes more time than the previous when it was working.
Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
---
meta/classes/image.bbclass | 9 +++++----
meta/classes/rootfs.bbclass | 3 +++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 813e1f3..d5c173b 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -346,17 +346,18 @@ DTB_IMG = "${PP_DEPLOY}/${@(d.getVar('DTB_FILES').split() or [''])[0]}"
do_copy_boot_files[dirs] = "${DEPLOY_DIR_IMAGE}"
do_copy_boot_files[lockfiles] += "${DEPLOY_DIR_IMAGE}/isar.lock"
do_copy_boot_files() {
- kernel="$(realpath -q '${IMAGE_ROOTFS}'/vmlinu[xz])"
+ set -x
+ kernel="$(realpath -q '${IMAGE_ROOTFS}'/vmlinu[xz] || true)"
if [ ! -f "$kernel" ]; then
- kernel="$(realpath -q '${IMAGE_ROOTFS}'/boot/vmlinu[xz])"
+ kernel="$(realpath -q '${IMAGE_ROOTFS}'/boot/vmlinu[xz] || true)"
fi
if [ -f "$kernel" ]; then
sudo cat "$kernel" > "${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE}"
fi
- initrd="$(realpath -q '${IMAGE_ROOTFS}/initrd.img')"
+ initrd="$(realpath -q '${IMAGE_ROOTFS}/initrd.img' || true)"
if [ ! -f "$initrd" ]; then
- initrd="$(realpath -q '${IMAGE_ROOTFS}/boot/initrd.img')"
+ initrd="$(realpath -q '${IMAGE_ROOTFS}/boot/initrd.img' || true)"
fi
if [ -f "$initrd" ]; then
cp -f "$initrd" '${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE}'
diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
index d19ac03..0d16754 100644
--- a/meta/classes/rootfs.bbclass
+++ b/meta/classes/rootfs.bbclass
@@ -33,6 +33,9 @@ rootfs_do_mounts[weight] = "3"
rootfs_do_mounts() {
sudo -s <<'EOSUDO'
set -e
+ for i in dev/shm dev/pts proc sys; do
+ mkdir -p '${ROOTFSDIR}/$i'
+ done
mountpoint -q '${ROOTFSDIR}/dev' || \
( mount -o bind,private /dev '${ROOTFSDIR}/dev' &&
mount -t tmpfs none '${ROOTFSDIR}/dev/shm' &&
--
2.34.1
https://16F0H.trk.elasticemail.com/tracking/unsubscribe?d=QeahcK7PAiv-rPg8_WzSoFK9wU1Dj448zICvk_Shcl3fpyE46OpdiQhGrWctPGvnA0CKh41O2LEKvTTWkq026QDrReKiFwphl8ET57WYvjKm0
reply other threads:[~2022-12-07 8:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4uil9nq8jkub.6oVt5dOuml8uqWJ9Z3m4rw2@16F0H.trk.elasticemail.com \
--to=roberto.foglietta@gmail.com \
--cc=isar-users@googlegroups.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