As a poorly-informed guess, maybe the OS X build is turning on
pre-compiled headers in a way ccache 2.4 can't cope well with?
--
Martin
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache
On 2010-09-14 21:43, Christopher Tate wrote:
> [...]
> Right now I'm doing some tests around using the new
> CCACHE_SLOPPINESS=file_macro tweak, and initial results are
> promising... but that begs the question of why the results on OSX with
> 2.4 are so poor in general.
>
> The obvious guess is t
We have a large cross-compilation environment that is essentially
identical on both Linux and MacOS X hosts. The build system uses
ccache to try to reduce redundant recompilation, but we're seeing
radically different outcomes on OSX versus Linux hosts. We're still
using ccache 2.4.
On Linux host
On Tue, Sep 14, 2010 at 5:20 PM, Joel Rosdahl wrote:
> I didn't know about this specific clash, but there are others very
> similar described in this bug report:
>
> https://bugzilla.samba.org/show_bug.cgi?id=7556
>
> You can create a new bug report if you want, or just leave a comment in
> 7556.
On 2010-09-14 12:23, Mehturt wrote:
> I tried to use ccache 3.0.1 with Sun's Studio 12 compiler.
> It seems to work just fine, except for some -x parameters that the
> compiler has, such as -xarch, -xtarget etc..
> The ccache thinks of the -x parameter as the language setting, which
> works only fo
Hi,
I tried to use ccache 3.0.1 with Sun's Studio 12 compiler.
It seems to work just fine, except for some -x parameters that the
compiler has, such as -xarch, -xtarget etc..
The ccache thinks of the -x parameter as the language setting, which
works only for gcc.
So is ccache supposed to work with
