[
https://issues.apache.org/jira/browse/IMPALA-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952379#comment-16952379
]
ASF subversion and git services commented on IMPALA-9034:
---------------------------------------------------------
Commit 3ae5f98420d685365e6fee6880732ee825492fd2 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=3ae5f98 ]
IMPALA-9034: fix distcc+ccache
According to the ccache manpage, the correct way to compose it with
distcc is to use CCACHE_PREFIX. I think this explains why local
ccache wasn't working for me.
I updated the distcc wrapper scripts to do this instead and
confirmed that it works - after doing a clean and rebuilding
the same branch, it is much faster and "ccache -s" shows a
bunch of cache hit.
ccache on the distcc server side still works.
Change-Id: Ie0b080709bd765056b9296d3deb805038fc01e5d
Reviewed-on: http://gerrit.cloudera.org:8080/14408
Reviewed-by: Andrew Sherman <[email protected]>
Tested-by: Tim Armstrong <[email protected]>
> ccache + distcc doesn't work with local ccache
> ----------------------------------------------
>
> Key: IMPALA-9034
> URL: https://issues.apache.org/jira/browse/IMPALA-9034
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.3.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Minor
>
> I've been noticing this for a while that ccache doesn't actually get local
> hits when I'm using distcc. I think I broke this with IMPALA-4701. It seems
> like the proper way to do wrapper scripts with ccache is to use CCACHE_PREFIX
> https://ccache.dev/manual/3.4.html#_using_ccache_with_other_compiler_wrappers.
> Anyway I played around with this and got it to work nicely and it makes local
> builds when switching branches much faster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
