Where are we on this patch? ---------------------------------------------------------------------------
Reini Urban wrote: > Dave Page schrieb: > > On Tue, Jun 24, 2008 at 9:32 AM, Magnus Hagander <[EMAIL PROTECTED]> 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 > -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
