From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 1/4] ccache: fix dirs creation
Date: Mon, 13 Feb 2023 09:56:08 +0200 [thread overview]
Message-ID: <20230213075611.5694-2-amikan@ilbers.de> (raw)
In-Reply-To: <20230213075611.5694-1-amikan@ilbers.de>
Create ccache debug directory only if CCACHE_DEBUG is enabled.
Also restore CCACHE_DIR creation if not exist.
Fixes 7956c4c ("add flag to enable ccache debug mode")
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta/classes/buildchroot.bbclass | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes/buildchroot.bbclass b/meta/classes/buildchroot.bbclass
index 5abd533..3d68d29 100644
--- a/meta/classes/buildchroot.bbclass
+++ b/meta/classes/buildchroot.bbclass
@@ -24,7 +24,10 @@ MOUNT_LOCKFILE = "${BUILDCHROOT_DIR}.lock"
buildchroot_do_mounts() {
if [ "${USE_CCACHE}" = "1" ]; then
- mkdir -p ${CCACHE_DIR}/debug
+ mkdir -p "${CCACHE_DIR}"
+ if [ "${CCACHE_DEBUG}" = "1" ]; then
+ mkdir -p "${CCACHE_DIR}/debug"
+ fi
fi
sudo -s <<'EOSUDO'
--
2.34.1
next prev parent reply other threads:[~2023-02-13 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:56 [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-02-13 7:56 ` Anton Mikanovich [this message]
2023-02-13 7:56 ` [PATCH v2 2/4] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 3/4] meta: unify cross selection Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13 8:01 ` [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-03-27 5:27 ` Uladzimir Bely
2023-03-28 15:51 ` Moessbauer, Felix
2023-03-28 15:56 ` Uladzimir Bely
2023-03-29 12:43 ` Moessbauer, Felix
2023-03-30 7:37 ` Uladzimir Bely
2023-04-02 18:44 ` Baurzhan Ismagulov
2023-04-05 11:56 ` Moessbauer, Felix
2023-04-05 13:28 ` Baurzhan Ismagulov
2023-04-10 5:44 ` Moessbauer, Felix
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=20230213075611.5694-2-amikan@ilbers.de \
--to=amikan@ilbers.de \
--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