Re: configure gaps

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: configure gaps
Date: 2011-03-10 20:14:03
Message-ID: 201103102014.p2AKE3R27850@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
>
> On 02/21/2011 09:33 PM, Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
> >>> I propose that we add the following test for this case:
> >>> AC_CHECK_HEADER(Python.h, [], [AC_MSG_ERROR([header file<Python.h>
> >>> is required for Python])])
> >> You'd need to pay attention to python_includespec, but otherwise seems
> >> reasonable.
> > Did this get done? If so, I don't see it.
>
> Oh, no. It skipped my TODO list. I'll try to get it done in the next day
> or so.

I have added this to the 9.1 open items list:

http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items#Code_Issues

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-10 20:14:51 Re: select_common_collation callers way too ready to throw error
Previous Message Peter Eisentraut 2011-03-10 20:05:42 Re: select_common_collation callers way too ready to throw error