public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 0/5] Fix ccache issues
Date: Wed, 11 Jan 2023 06:49:09 +0000	[thread overview]
Message-ID: <0a0f5f75099dd5ac60c191c4829e13afc9587e74.camel@siemens.com> (raw)
In-Reply-To: <20221219142933.12437-1-amikan@ilbers.de>

On Mon, 2022-12-19 at 17:29 +0300, Anton Mikanovich wrote:
> This patchset just fixes some ccache-related issues which prevented
> us
> from enabling ccache globally.

Hi Anton,

with recent ISAR versions, we frequently see the following error in the
do_dpkg_build tasks (no matter if this series is applied or not):

ccache: error: Failed to create directory /ccache/5/d: Not a directory

There have to be more cases where the /ccache directory is either not
created or created with wrong access rights.

Felix

> 
> Anton Mikanovich (5):
>   ccache: fix dirs creation
>   ccache: fix CCACHE_DIR owner for sbuild
>   dpkg-base: remove deprecated code
>   meta: unify cross selection
>   ccache: separate cache based on cross compile
> 
>  meta/classes/buildchroot.bbclass | 23 +++++----------------
>  meta/classes/crossvars.bbclass   | 34
> ++++++++++++++++++++++++++++++++
>  meta/classes/dpkg-base.bbclass   | 29 +--------------------------
>  meta/classes/dpkg.bbclass        |  2 +-
>  meta/classes/sbuild.bbclass      | 19 ++----------------
>  meta/classes/sdk.bbclass         | 17 +++-------------
>  meta/conf/bitbake.conf           |  2 +-
>  7 files changed, 47 insertions(+), 79 deletions(-)
>  create mode 100644 meta/classes/crossvars.bbclass
> 
> -- 
> 2.17.1
> 


      parent reply	other threads:[~2023-01-11  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:29 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
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 ` Moessbauer, Felix [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=0a0f5f75099dd5ac60c191c4829e13afc9587e74.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=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