Re: _GNU_SOURCE

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 16:53:36
Message-ID: 9691.1064768016@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:
> Jeroen Ruigrok/asmodai wrote:
>> "The crypt_r function is a GNU extension."

> BSD/OS doesn't have crypt_r(), and crypt() manual page says:

> The crypt() function may not be safely called concurrently from multiple
> threads, e.g., the interfaces described by pthreads(3).

Right. But whether crypt is re-entrant or not isn't really the issue
here. The problem is that the standard RHL 8 version of Perl is
installed in such a way that <perl.h> fails to compile unless crypt_r's
struct typedef is visible. I have not looked, but I surmise this must
mean that they configured Perl with _GNU_SOURCE defined. Maybe it was
done so Perl could get at crypt_r, but more likely it was for some other
reasons altogether ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2003-09-28 17:48:01 Re: pg_dump doesn't dump binary compatible casts
Previous Message Bruce Momjian 2003-09-28 16:37:25 Re: _GNU_SOURCE