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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-07-01 21:51:28
Message-ID: 51D1F9E0.4040506@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 07/01/2013 05:35 PM, Peter Eisentraut wrote:
> On 7/1/13 9:19 AM, Tom Lane wrote:
>> AFAICT, the result in this case would be that the script comes to the
>> wrong conclusion about whether ucred.h is available. Wouldn't that
>> result in a build failure, or at least missing features? IOW, don't
>> we need to fix this test anyway?
> The test needs to be fixed, but with a newer Autoconf version we would
> (probably) have been alerted about that by a build failure rather than
> someone scanning build logs.

I take it you mean a configure failure would occur with a later Autoconf.

cheers

andrew

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2013-07-01 22:43:02 Re: BUG #8269: the recovery_target_inclusive is always considered as false
Previous Message Peter Eisentraut 2013-07-01 21:35:33 Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled