From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Black <daniel.black@au1.ibm.com>
In-reply-to: <773008e7-db08-a525-c887-de9aee60fdce@au.ibm.com>
References: <773008e7-db08-a525-c887-de9aee60fdce@au.ibm.com>
Comments: In-reply-to Daniel Black <daniel.black@au1.ibm.com>
 message dated "Mon, 05 Sep 2016 16:08:09 +1000"
Date: Wed, 07 Sep 2016 22:12:09 -0400
Message-ID: <15598.1473300729@sss.pgh.pa.us>
Cc: pgbuildfarm-members@lists.pgfoundry.org
Subject: Re: [Pgbuildfarm-members] new build members
Precedence: list
Content-Length: 1013
Lines: 24

Daniel Black <daniel.black@au1.ibm.com> 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%3A53&stg=make
contains something north of 1000 warnings, most of which are entirely
bogus.  Makes it hard to see if there are any that are meaningful.

			regards, tom lane