You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2017/03/29 23:20:41 UTC

[jira] [Created] (KUDU-1961) devtoolset-3 defeats ccache

Adar Dembo created KUDU-1961:
--------------------------------

             Summary: devtoolset-3 defeats ccache
                 Key: KUDU-1961
                 URL: https://issues.apache.org/jira/browse/KUDU-1961
             Project: Kudu
          Issue Type: Bug
          Components: build
    Affects Versions: 1.4.0
            Reporter: Adar Dembo


When devtoolset-3 is used (via enable_devtoolset.sh on el6), it's quite likely that ccache will go used for the build. Certainly for build-thirdparty.sh, and likely for the main Kudu build too (unless you go out of your way to set CC/CXX=ccache when invoking cmake).

We should be able to fix this in enable_devtoolset.sh, at least in the common case where symlinks to ccache named after the compiler are on the PATH. We could ensure that, following the call to 'scl enable devtoolset-3 <cmd>', ccache symlinks are placed at the head of the PATH, before /opt/rh/devtoolset-3/, and only then is <cmd> actually invoked. This should cause ccache to be used, and it'll chain to the devtoolset-3 compiler because /opt/rh/devtoolset-3/ is ahead of /usr/bin on the PATH. We may need an intermediate script to do this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)