| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Jeroen Ruigrok/asmodai" <asmodai(at)wxs(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: _GNU_SOURCE |
| Date: | 2003-09-28 15:48:04 |
| Message-ID: | 9219.1064764084@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> _GNU_SOURCE All of the above, plus GNU extensions.
>>
>> Which means it enables all this:
>>
>> __STRICT_ANSI__, _ISOC99_SOURCE, _POSIX_SOURCE, _POSIX_C_SOURCE,
>> _XOPEN_SOURCE, _XOPEN_SOURCE_EXTENDED, _LARGEFILE_SOURCE,
>> _LARGEFILE64_SOURCE, _FILE_OFFSET_BITS=N, _BSD_SOURCE, _SVID_SOURCE
Hm. So is crypt_r() a GNU extension? I would've thought it was
specified by some standard or other. Perhaps the real issue here
is that /usr/include/crypt.h is using the wrong control symbol.
At least in RHL 8.0, it definitely uses __USE_GNU to hide crypt_r
and the associated struct type.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-28 16:02:43 | Re: [SQL] plpgsql doesn't coerce boolean expressions to |
| Previous Message | Tom Lane | 2003-09-28 15:36:54 | Re: pgsql-server/src/backend catalog/index.c comma ... |