From ef33a3138384667f819688141086102e6e83ec44 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Mon, 10 Jul 2017 16:31:31 +0100 Subject: ccache: don't export CCACHE_DISABLE globally CCACHE_DISABLE was added to bitbake.conf in oe-core dd2bab (June 2012) because autogen-native exports HOME=/dev/null during the build, which is then used by a host ccache to construct the path to it's cache (/dev/null/.ccache) and this fails. However we now always export CCACHE_DIR to solve the same problem in a more efficient way so CCACHE_DISABLE can be deleted. Signed-off-by: Ross Burton --- meta/classes/ccache.bbclass | 1 - 1 file changed, 1 deletion(-) (limited to 'meta/classes/ccache.bbclass') diff --git a/meta/classes/ccache.bbclass b/meta/classes/ccache.bbclass index d58c8f6e57..9f1b1f45e3 100644 --- a/meta/classes/ccache.bbclass +++ b/meta/classes/ccache.bbclass @@ -1,6 +1,5 @@ CCACHE = "${@bb.utils.which(d.getVar('PATH'), 'ccache') and 'ccache '}" export CCACHE_DIR ?= "${TMPDIR}/ccache/${MULTIMACH_TARGET_SYS}/${PN}" -CCACHE_DISABLE[unexport] = "1" # We need to stop ccache considering the current directory or the # debug-prefix-map target directory to be significant when calculating -- cgit 1.2.3-korg