Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled
От | Tom Lane |
---|---|
Тема | Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled |
Дата | |
Msg-id | 7051.1372600177@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: BUG #8271: Configure warning: sys/ucred.h: present but
cannot be compiled
|
Список | pgsql-bugs |
Andrew Dunstan <andrew@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. regards, tom lane
В списке pgsql-bugs по дате отправления: