Bruce Momjian schrieb:
> Andrew Dunstan wrote:
>>
>> Bruce Momjian wrote:
>>> Andrew Dunstan wrote:
>>>
>>>> Alvaro Herrera wrote:
>>>>
>>>>> Andrew Dunstan wrote:
>>>>>
>>>>>
>>>>>> I'm confused. There is a Cygwin member of buildfarm, working quite
>>>>>> happily. Can you point me to the exact patch in question, please? I
>>>>>> thought we resolved the matter of stat() ages ago.
>>>>>>
>>>>>>
>>>>> http://archives.postgresql.org/message-id/4865F707.6010702%40x-ray.at
>>>>>
>>>>>
>>>>>
>>>> That patch is NOT about $subject. In fact, if you read that whole thread
>>>> you will see here
>>>> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00915.php that I
>>>> conducted a test on Cygwin and found it was not suffering from the
>>>> problem we fixed on WIN32.
>>>>
>>>> AFAICT Reini's patch is about fixing OpenSSL and possibly some other
>>>> options on Cygwin. It was rejected because it had other problems, but is
>>>> not indicative of a fundamental problem on Cygwin. There is no reason I
>>>> am aware of that we should declare Cygwin no longer supported, no matter
>>>> how much its continued existence apparently annoys a few people :-) .
>>>>
>>> Oh, good, thanks for clearing that up. So should we just document that
>>> OpenSSL doesn't work on Cygwin and call this item closed?
>>>
>>>
>> This item should be closed. We should see if Reini can submit an
>> acceptable patch for OpenSSL.
>
> I have documented that OpenSSL is not supported for Cygwin.
Excuse me?
openssl works fine on cygwin, even without the testing patch which was
attached. This patch only tried to optimize openssl socket handling
equivalent to WIN32.
Please revert that documentation.
The current configure args of the official postgresql packages are:
--enable-nls --with-openssl --with-perl --with-python --with-ldap
The problem is just that SSPI auth does not compile on cygwin.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/