Re: _GNU_SOURCE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: _GNU_SOURCE
Date
Msg-id 9219.1064764084@sss.pgh.pa.us
Whole thread Raw
In response to _GNU_SOURCE  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: _GNU_SOURCE  (Jeroen Ruigrok/asmodai <asmodai@wxs.nl>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: _GNU_SOURCE
Next
From: Tom Lane
Date:
Subject: Re: [SQL] plpgsql doesn't coerce boolean expressions to