<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - ccache does not get any hits on 'make sc' just after 'make sc.clean'" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129632#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - ccache does not get any hits on 'make sc' just after 'make sc.clean'" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129632">bug 129632</a> from <a class="email" href="mailto:l.lunak@collabora.com" title="Luboš Luňák <l.lunak@collabora.com>"> Luboš Luňák</a> <pre>I assume you previously didn't get colored gcc output? Your problem is not a bug, it's simply the way it is. Ccache does not share "identical" compilations if they differ in colorization, because, well, they do differ - there's a whole section on this in the ccache manual or in a github request or somewhere. So if you want it to work the same way as before, unset gb_COLOR (with the price of not having any colors). Or always force gb_COLOR and accept that the redirected output will have escape sequences. Or do not do anything and accept that ccache does not share these. Or do not run your large build with redirected output. Or find the ccache request with details and improve ccache to be smart about sharing them. But whatever you do, there's a drawback. And then there's the issue of gbuild trying to be (too) smart and doing a lot of stuff that it probably shouldn't be doing. But that's not limited to just this, there's a whole load of things that gbuild messes with and probably shouldn't (compiler colorization, make parallelism, icecream setup, whatnot).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>