public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
To: Daniel Black <[email protected]>
Cc: [email protected]
Subject: Re: [Pgbuildfarm-members] new build members
Date: Thu, 8 Sep 2016 09:18:38 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
List-Unsubscribe:  <http://lists.pgfoundry.org/mailman/options/pgbuildfarm-members>, <mailto:[email protected]?subject=unsubscribe>



On 09/07/2016 10:12 PM, Tom Lane wrote:
> Daniel Black <[email protected]> writes:
>> I've configured a bunch of builds to add to the build farm. The list is:
> Hi Daniel!  Thanks for bringing all those new critters online.
> However, may I suggest that the ccache+clang ones would be a lot more
> useful if you added this to their configuration:
>
>      build_env =>{
>
> +        # needed to make ccache play nice with clang
> +        CCACHE_CPP2 => '1',
>
> Lack of this option is what's causing a lot of those useless warnings
> (it has to do with clang being fed preprocessor output, which triggers
> some of its more dubious warning heuristics).  I think this has become
> the default behavior as of ccache 3.3, but in older versions you gotta
> ask for it.
>
> As an example of the importance of this,
> http://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=devario&dt=2016-09-08%2000%3A44%3A5...
> contains something north of 1000 warnings, most of which are entirely
> bogus.  Makes it hard to see if there are any that are meaningful.


As of ccache version 3.3.1 this is apparently the default - see 
<https://ccache.samba.org/manual.html;

I guess I should put it in the sample config file to cater for older 
versions (e.g. my Fedora machine has 3.2.3 where it is apparently not 
the default).


cheers

andrew

view thread (3+ messages)

reply

Reply instructions:

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

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [Pgbuildfarm-members] new build members
  In-Reply-To: <[email protected]>

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

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox