From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 4/4] ccache: separate cache based on cross compile
Date: Mon, 13 Feb 2023 09:56:11 +0200 [thread overview]
Message-ID: <20230213075611.5694-5-amikan@ilbers.de> (raw)
In-Reply-To: <20230213075611.5694-1-amikan@ilbers.de>
Mixing ccache generated by cross and native compilers makes the second
run to stuck all the build.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
doc/user_manual.md | 3 ++-
meta/conf/bitbake.conf | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index b9a0bb6..61d1390 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -1008,7 +1008,8 @@ to `local.conf`. If some package requires ccache to be always disabled,
By default, ccache directory is created inside `TMPDIR`, but it can be
adjusted by `CCACHE_TOP_DIR` variable in `local.conf`. Ccache directory
-`CCACHE_DIR` default value is `"${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}"`,
+`CCACHE_DIR` default value is
+`"${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}-${BUILD_HOST_ARCH}"`,
that means caches for different distros and architectures are not overlapped.
The ccache debug mode can be enabled by setting `CCACHE_DEBUG = "1"`
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 522241a..e6956c3 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -153,7 +153,7 @@ INHERIT += "${@'buildstats' if d.getVar('USE_BUILDSTATS') == '1' else ''}"
# Default values for ccache
USE_CCACHE ??= "0"
CCACHE_TOP_DIR ?= "${TMPDIR}/ccache"
-CCACHE_DIR ?= "${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}"
+CCACHE_DIR ?= "${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}-${BUILD_HOST_ARCH}"
CCACHE_DEBUG ?= "0"
# Variables for tasks marking
--
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 ` [PATCH v2 1/4] ccache: fix dirs creation Anton Mikanovich
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 ` Anton Mikanovich [this message]
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-5-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