Happens with net-im/kadu 4.3-r1, was happening with some older versions/revisions too. example related output lines: P : /var/ccache A: /var/ccache R: /var/ccache C: ccache /usr/bin/x86_64-pc-linux-gnu-g++ -DKADU_EXPORT_TESTS [cut] Steps to reproduce: - install ccache, - make sure /var/ccache exists, - have disabled ccache (FEATURES="-ccache"), - emerge Kadu. On systems that have dev-util/ccache installed but disabled, a possible workaround is to make sure /var/ccache does not exist. A possible workaround (doable without chaning the build system) usable in ebuild is to call cmake with -DCCACHE_FOUND=OFF. (Like in jsoncpp-1.8.0.ebuild.) Culprit - this being done in CMakeLists.txt: ## CCache is cool stuff to improve compilation time find_program (CCACHE_FOUND ccache) if (CCACHE_FOUND) set_property (GLOBAL PROPERTY RULE_LAUNCH_COMPILE ccache) set_property (GLOBAL PROPERTY RULE_LAUNCH_LINK ccache) endif (CCACHE_FOUND) configuration: Portage 2.3.5 (python 2.7.12-final-0, default/linux/amd64/13.0/desktop, gcc-4.9.3-vanilla, glibc-2.23-r4, 4 .4.0-sabayon x86_64) ccache version 3.3.4 [disabled]
Strange, I'm unable to reproduce, I do have non-standard ccache location but sandbox should have caught that. Anyway, we cannot use CMake mechanism of handling ccache regardless, rather our CC/CXX compiler path overrides. Thanks for reporting and investigation. Please reopen if that somehow didn't work.
