DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] FYI: Using ccache a linux compiler caching tool with DPDK
Date: Mon, 27 Jun 2016 22:45:39 +0200	[thread overview]
Message-ID: <5578887.p7vRAffkie@xps13> (raw)
In-Reply-To: <D1F8540A-0C26-47C2-B60B-E3C017A40522@intel.com>

2016-06-27 18:10, Wiles, Keith:
> It appears the ccache and clang have a few problems without the global having the environment variable set:
> export CCACHE_CPP2=yes
> 
> Without this environment variable clang starts to complain about a number of issues. If you see a compile problem please rebuild with ccache disabled using ‘sudo CCACHE_DISABLE=true …’ or uninstall ccache ‘sudo apt-get remove ccache’

With ccache 3.2, it is possible to replace the environment variable
CCACHE_CPP2=yes by the configuration run_second_cpp=true in ccache.conf.

See http://peter.eisentraut.org/blog/2014/12/01/ccache-and-clang-part-3/

> It is possible that GCC will also have compiler issues, but I do not seem to see any, just try without ccache to verify.
> 
> Here is a link to help explain more details:
> See e.g. http://petereisentraut.blogspot.com/2011/09/ccache-and-clang-part-2.html
> 
> If the build works then I have not found any issues with using ccache except a faster build time ☺  YMMV 
> 
> Regards,
> Keith

      reply	other threads:[~2016-06-27 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 18:10 Wiles, Keith
2016-06-27 20:45 ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5578887.p7vRAffkie@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).