From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Cronenworth <mike(at)cchtml(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Fix Windows socket error checking for MinGW |
Date: | 2013-08-17 19:33:46 |
Message-ID: | 20130817193346.GA555417@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Aug 17, 2013 at 02:04:24PM -0400, Andrew Dunstan wrote:
>> On Fri, Aug 16, 2013 at 06:56:45PM -0500, Michael Cronenworth wrote:
>>> +#ifndef WIN32
>>> if (SOCK_ERRNO == EWOULDBLOCK)
>>> +#else
>>> + if (SOCK_ERRNO == WSAEWOULDBLOCK)
>>> +#endif
> We don't seem to have a problem with this on native builds, only on
> cross-compiles AFAIK (see buildfarm for proof). The native mingw-w64
> build works just fine. So my first question is going to be why is the
> cross-compile different?
One of the reports Michael cited was apparently "native":
http://www.postgresql.org/message-id/E1UcLPd-0000L4-TI@wrigleys.postgresql.org
Perhaps only some versions of w32api trigger the problem. I agree we ought to
understand the necessary conditions before proceeding.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2013-08-17 19:39:21 | Re: psql missing tab completion for extensions |
Previous Message | Peter Geoghegan | 2013-08-17 18:15:03 | Re: [HACKERS] Chinese in Postgres |