| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: python cleanup |
| Date: | 2011-07-25 14:40:41 |
| Message-ID: | 4E2D8069.10303@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/25/2011 10:36 AM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> [python headers set _POSIX_C_SOURCE and _XOPEN_SOURCE]
> BTW ... so far as I can find, there is no attempt anywhere in the
> Postgres sources to set either of these macros. And my understanding of
> their purpose is that *system* headers should not be setting them at
> all, rather the application sets them to indicate which POSIX feature
> level it would like. So perhaps the real question here is where the
> heck are your conflicting values coming from ...
>
>
_POSIX_C_SOURCE at least is defined in features.h, which is included by
huge numbers of system headers, many of which are included by c.h.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-07-25 14:51:53 | Re: Environment checks prior to regression tests? |
| Previous Message | Tom Lane | 2011-07-25 14:36:01 | Re: python cleanup |