Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Emre Hasegeli <emre(at)hasegeli(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
Date: 2013-06-30 13:49:37
Message-ID: 7051.1372600177@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andrew Dunstan <andrew(at)dunslane(dot)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(at)postgresql(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Dunstan 2013-06-30 14:17:50 Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
Previous Message Andrew Dunstan 2013-06-30 13:38:22 Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled