Re: next: ccache broken for cross-compiling

[Henning Schild <henning.schild@siemens.com>]

In order to find what might be going wrong you could enable ccache
logging. setting "log_file = /tmp/ccache.log" in ccache.conf (in the
caches main directory)

Double check it is actually used, i think it would need CCACHE_DIR in
env and some compiler wrappers prefixed in PATH, plus write permissions
on the files.

You can watch the thing from anywhere where it is mounted

CCACHE_DIR=/path/to/cache watch ccache

If you see missing going up but not hits ... it is probably used but
for some reason does not like what it found. Felix once pointed out
that for the kernel that could be if you have debug flags enabled,
where the absolute path of the sources will always end up in the
binaries. Or it could simply be that with sbuild the location of the
sources changes too dramatic ... in which case "hash_dir = false" could
help in the ccache.conf

Henning

Am Sun, 10 Jul 2022 22:51:14 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> Hi all,
> 
> I've noticed that ccache is not doing its job with current next when
> cross-building, e.g. mc:qemuarm64-bullseye:linux-mainline. It does
> work as expected for native builds
> (mc:qemuamd64-bullseye:linux-mainline), and it works fine with v0.9.
> Seems like an sbuild regression.
> 
> Jan
>