Don't the release notes of the next version address this? https://ccache.samba.org/releasenotes.html#_ccache_3_2_6
On Thu, 30 Jun 2016 23:08:05 +0200 Joel Rosdahl <j...@debian.org> wrote: > Thanks for the bug report. I have reproduced the issue, see the attached > script. Yes, to trigger the bug, the source file path must be absolute and > CCACHE_BASEDIR must be enabled. > > The behavior change in question comes from this commit: < > https://github.com/ccache/ccache/commit/2df269a3121889ebcdfa5d98dfb4d675f690e039>. > It's included in ccache 3.1.8 and newer. > > Not sure what to do, though. Have to think about it some more. > > -- Joel > > On 30 June 2016 at 14:15, Stefan Fritsch <s...@sfritsch.de> wrote: > > > found 829088 3.2.5-1 > > thanks > > > > Version 3.2.5-1 is also affected by this issue. > > > > Attached is a log file from that version. > > > > Since the path names are rather complicated in the examples: The dir with > > the symlinked source files is (note the obj in the 3rd component): > > > > > > /changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc-minimal/libc/src/libc/stdlib/malloc-standard/free.c > > > > The path to the source file with all symlinks resolved is (there is no > > obj/ and no amd64/ in this path): > > > > > > /changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c
