Re: _GNU_SOURCE - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: _GNU_SOURCE
Date
Msg-id 200310090340.h993e7o29716@candle.pha.pa.us
Whole thread Raw
In response to Re: _GNU_SOURCE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: _GNU_SOURCE
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.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 ...

Do we want to try this approach that the DBD:pg guys are using?
http://gborg.postgresql.org/pipermail/dbdpg-general/2003-September/000452.html

It involves "$Config{q{ccflags}};".  I think they can use it because
they are using Makefile.PL, while our plperl is not, so maybe we can't
use it.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: Autovacuum readme
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: missing COMMENT ON objects