From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/5] ccache: fix dirs creation
Date: Wed, 8 Feb 2023 10:01:55 +0200 [thread overview]
Message-ID: <ed21d479-1896-9b1d-991f-2db73e334b16@ilbers.de> (raw)
In-Reply-To: <20221219162130.0cae38cf@md1za8fc.ad001.siemens.net>
19/12/2022 17:21, Henning Schild wrote:
> Am Mon, 19 Dec 2022 17:29:29 +0300
> schrieb Anton Mikanovich <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 b4ff2886..72eb80bc 100644
>> --- a/meta/classes/buildchroot.bbclass
>> +++ b/meta/classes/buildchroot.bbclass
>> @@ -25,7 +25,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
> I guess one could skip that -p, but it does not hurt.
>
> Henning
I've used '-p' here to skip errors on 'already exist' cases.
>> + fi
>> fi
>>
>> sudo -s <<'EOSUDO'
next prev parent reply other threads:[~2023-02-08 8:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 14:29 [PATCH 0/5] Fix ccache issues Anton Mikanovich
2022-12-19 14:29 ` [PATCH 1/5] ccache: fix dirs creation Anton Mikanovich
2022-12-19 15:21 ` Henning Schild
2023-02-08 8:01 ` Anton Mikanovich [this message]
2022-12-20 2:39 ` Moessbauer, Felix
2022-12-19 14:29 ` [PATCH 2/5] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2022-12-19 15:23 ` Henning Schild
2022-12-20 2:40 ` Moessbauer, Felix
2023-01-12 10:00 ` Moessbauer, Felix
2023-02-08 8:15 ` Anton Mikanovich
2022-12-19 14:29 ` [PATCH 3/5] dpkg-base: remove deprecated code Anton Mikanovich
2022-12-19 14:29 ` [PATCH 4/5] meta: unify cross selection Anton Mikanovich
2022-12-20 2:49 ` Moessbauer, Felix
2022-12-19 14:29 ` [PATCH 5/5] ccache: separate cache based on cross compile Anton Mikanovich
2022-12-20 2:59 ` Moessbauer, Felix
2023-01-11 6:49 ` [PATCH 0/5] Fix ccache issues 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=ed21d479-1896-9b1d-991f-2db73e334b16@ilbers.de \
--to=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--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