From: Anton Mikanovich <amikan@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/4] Fix ccache issues
Date: Mon, 13 Feb 2023 10:01:03 +0200 [thread overview]
Message-ID: <d5fed356-b320-3e17-b237-6ce974335dfe@ilbers.de> (raw)
In-Reply-To: <20230213075611.5694-1-amikan@ilbers.de>
13/02/2023 09:56, Anton Mikanovich wrote:
> This patchset just fixes some ccache-related issues which prevented us
> from enabling ccache globally.
>
> Changes since v1:
> - Rebased on next
> - Addressed previous feedback
>
There are some ccache related issues still not fixed in this version of the
patchset. This is why USE_CCACHE still did not enabled by default.
We will continue investigation but it will probably takes some time. So
going
one step closer to clean colution looks also ok for now.
next prev parent reply other threads:[~2023-02-13 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:56 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 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13 8:01 ` Anton Mikanovich [this message]
2023-03-27 5:27 ` [PATCH v2 0/4] Fix ccache issues 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=d5fed356-b320-3e17-b237-6ce974335dfe@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