From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Black <daniel(dot)black(at)au1(dot)ibm(dot)com> |
Cc: | pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org |
Subject: | Re: [Pgbuildfarm-members] new build members |
Date: | 2016-09-08 02:12:09 |
Message-ID: | 15598.1473300729@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
Daniel Black <daniel(dot)black(at)au1(dot)ibm(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2016-09-08 13:18:38 | Re: [Pgbuildfarm-members] new build members |
Previous Message | Daniel Black | 2016-09-05 06:08:09 | [Pgbuildfarm-members] new build members |