From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 5/5] allow to switch CCACHE_DEBUG mode from environment
Date: Mon, 1 Aug 2022 16:57:19 +0200 [thread overview]
Message-ID: <20220801145719.546953-6-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20220801145719.546953-1-felix.moessbauer@siemens.com>
This patch whitelists the CCACHE_DEBUG variable to simplify
ccache debugging. It now can be set from the environment where bitbake
is invoked.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
scripts/isar-buildenv-internal | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/isar-buildenv-internal b/scripts/isar-buildenv-internal
index ec8e4377..d202e5f9 100755
--- a/scripts/isar-buildenv-internal
+++ b/scripts/isar-buildenv-internal
@@ -77,5 +77,5 @@ export PATH
BBPATH="${BUILDDIR}"
export BBPATH
-BB_ENV_EXTRAWHITE="BITBAKEDIR SCRIPTSDIR TESTSUITEDIR http_proxy https_proxy ftp_proxy no_proxy GNUPGHOME"
+BB_ENV_EXTRAWHITE="BITBAKEDIR SCRIPTSDIR TESTSUITEDIR http_proxy https_proxy ftp_proxy no_proxy GNUPGHOME CCACHE_DEBUG"
export BB_ENV_EXTRAWHITE
--
2.30.2
next prev parent reply other threads:[~2022-08-01 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:57 [PATCH 0/5] Improve debug infrastructure for build debugging Felix Moessbauer
2022-08-01 14:57 ` [PATCH 1/5] get architecture specific build deps for devshell Felix Moessbauer
2022-08-01 14:57 ` [PATCH 2/5] move CCACHE_DISABLE env var to function Felix Moessbauer
2022-08-01 14:57 ` [PATCH 3/5] prepend ccache wrappers in devshell Felix Moessbauer
2022-08-01 15:00 ` Jan Kiszka
2022-08-02 7:50 ` Felix Moessbauer
2022-08-01 14:57 ` [PATCH 4/5] do not warn on CCACHE related variables Felix Moessbauer
2022-08-01 14:57 ` Felix Moessbauer [this message]
2022-08-10 11:32 ` [PATCH 0/5] Improve debug infrastructure for build debugging Anton Mikanovich
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=20220801145719.546953-6-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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