On 06/30/2013 09:49 AM, Tom Lane wrote:
Andrew Dunstan <and...@dunslane.net> writes:
On 2013-06-30 15:17:20 +0200, Andres Freund wrote:
Andrew: Could we perhaps check for the "Report this to" bit in the
buildfarm?
I'm not sure what you're asking here.
I think he's wishing that if configure prints something like
configure: WARNING: sys/ucred.h: present but cannot be compiled
configure: WARNING: sys/ucred.h: check for missing prerequisite headers?
configure: WARNING: sys/ucred.h: see the Autoconf documentation
configure: WARNING: sys/ucred.h: section "Present But Cannot Be Compiled"
configure: WARNING: sys/ucred.h: proceeding with the preprocessor's result
configure: WARNING: sys/ucred.h: in the future, the compiler will take
precedence
configure: WARNING: ## ---------------------------------------- ##
configure: WARNING: ## Report this to pgsql-bugs@postgresql.org ##
configure: WARNING: ## ---------------------------------------- ##
that that ought to be treated as a failure not a success. I'm not
entirely sure that I agree, but it's an arguable position.
Oh. Well, if that's a failure then it's up to configure to treat it as
one. The buildfarm doesn't second-guess the exit status of the various
steps, and it doesn't report warnings - if it did we'd be flooded.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
