Skip site navigation (1) Skip section navigation (2)

Re: stat() vs cygwin

From: Reini Urban <rurban(at)x-ray(dot)at>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: stat() vs cygwin
Date: 2008-06-28 08:32:07
Message-ID: 4865F707.6010702@x-ray.at (view raw or flat)
Thread:
Lists: pgsql-hackers
Dave Page schrieb:
> On Tue, Jun 24, 2008 at 9:32 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Yes.
>>
>> As in the cygwin build does build. Nobody really has verified if the fix
>> is needed there. But frankly, if you are likely to care about the
>> effects of this issue, you won't be running cygwin anyway. It's mostly a
>> dead platform for postgresql anyway, AFAICS we only keep it building for
>> legacy compatibility. Once it starts taking lots of resources to keep
>> building (which it doesn't now), I think we should just drop it instead...

"Dead" is interesting. We see a lot of cygwin users having postgresql 
installed.

> FWIW, the most recent packages from Cygwin themselves are 8.2.5.

Update: 8.2.9 is latest.
8.3.x not because the new SSPI doesn't work yet.

currently failing is: --with-gssapi --with-krb5 --with-tcl --with-java 
--with-ossp-uuid --with-ldap
(but ldap works okay with 8.2.9)

currently testing is: --enable-nls --with-CXX --with-openssl --with-perl 
--with-python --with-libxml --with-libxslt

current cygwin patch in testing is attached.
-- 
Reini Urban
postgresql cygwin maintainer


Attachment: postgresql-8.3.3-1.src.patch
Description: text/x-patch (20.6 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Hans-Juergen SchoenigDate: 2008-06-28 08:46:01
Subject: interval madness ...
Previous:From: Jean-Michel PouréDate: 2008-06-28 07:44:50
Subject: Re: XML index support

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group