Bug#829088: ccache may silently miscompile symlinked source files

On 15 July 2016 at 07:55, Jaap Keuter wrote: > Don't the release notes of the next version address this? > https://ccache.samba.org/releasenotes.html#_ccache_3_2_6 Yes, it's a fix for this bug. I also made a 3.1.12 release especially for Debian stable. I just haven't had

Bug#829088: ccache may silently miscompile symlinked source files

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 wrote: > Thanks for the bug report. I have reproduced the issue, see the attached > script. Yes, to trigger the

Bug#829088: ccache may silently miscompile symlinked source files

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: <

Bug#829088: ccache may silently miscompile symlinked source files

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):

Bug#829088: ccache may silently miscompile symlinked source files

Package: ccache Version: 3.1.10-1 Severity: grave Hi, the ccache in jessie has a serious regression vs. wheezy. When passing files to the preprocessor, ccache in jessie resolves symlinks and passes the path of the resulting filename on the preprocessor command line. This does however change