| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-ports(at)postgresql(dot)org |
| Subject: | Re: Cygwin PostgreSQL CVS Patch Question |
| Date: | 2001-01-09 23:34:33 |
| Message-ID: | 7644.979083273@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-ports |
Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com> writes:
>> Er, why should it? With the code as it stands, configure should decide
>> that Cygwin doesn't HAVE_SYS_NERR, and so nothing will reference
>> sys_nerr.
> Unfortunately, the above is not true:
> $ configure
> ...
> checking for sys_nerr... yes
That's pretty darn interesting. The configure check looks bulletproof
to me:
[AC_TRY_LINK([extern int sys_nerr;],
[int x = sys_nerr;],
Would you poke into it and figure out how this is succeeding, if there's
not any sys_nerr variable exported from the C library?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-01-09 23:37:31 | Re: Re: Cygwin PostgreSQL CVS Patch Question |
| Previous Message | Jason Tishler | 2001-01-09 23:16:14 | Re: Re: Cygwin PostgreSQL CVS Patch Question |