From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH 0/5] Improve debug infrastructure for build debugging
Date: Wed, 10 Aug 2022 14:32:28 +0300 [thread overview]
Message-ID: <0c9b3fba-c5dd-95e4-fe74-6f05cd029678@ilbers.de> (raw)
In-Reply-To: <20220801145719.546953-1-felix.moessbauer@siemens.com>
01.08.2022 17:57, Felix Moessbauer wrote:
> Patch 1: Fix crossbuild in devshell
> Patch 2,3: Fix ccache integration in devshell
> Patch 4: do not warn about variables in case CCACHE_DEBUG is enabled
> Patch 5: allow to set CCACHE_DEBUG from calling environment
>
> This series helps a lot to find and solve cachability issues in
> kernel (cross) builds.
>
> Best regards,
> Felix
>
> Felix Moessbauer (5):
> get architecture specific build deps for devshell
> move CCACHE_DISABLE env var to function
> prepend ccache wrappers in devshell
> do not warn on CCACHE related variables
> allow to switch CCACHE_DEBUG mode from environment
>
> meta/classes/base.bbclass | 2 ++
> meta/classes/dpkg-base.bbclass | 10 ++++++++--
> meta/classes/dpkg.bbclass | 5 +++--
> scripts/isar-buildenv-internal | 2 +-
> 4 files changed, 14 insertions(+), 5 deletions(-)
>
Applied to next, thanks.
prev parent reply other threads:[~2022-08-10 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:57 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 ` [PATCH 5/5] allow to switch CCACHE_DEBUG mode from environment Felix Moessbauer
2022-08-10 11:32 ` Anton Mikanovich [this message]
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=0c9b3fba-c5dd-95e4-fe74-6f05cd029678@ilbers.de \
--to=amikan@ilbers.de \
--cc=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