From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Call for port reports |
Date: | 2004-12-07 00:25:11 |
Message-ID: | 41B4F867.80608@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>I have started filling in the supported platform list for the 8.0.0
>release with the information from the build farm:
>
>http://developer.postgresql.org/docs/postgres/supported-platforms.html
>
>It's now time to fill the holes. Briefly, I'm looking for exit status 0
>on
>
>./configure --prefix=SOMEWHERE --enable-thread-safety --with-tcl \
>--with-perl --with-python --with-krb5 --with-pam -with-openssl
>make
>make install
>make check
>
>
buildfarm actually runs in this order:
make
make check
make contrib
make install
... more steps
I assume that's ok.
>with PostgreSQL 8.0.0rc1 or later. If you know what you're doing, you
>can also try other options, but please tell what you did.
>
>(I would like the build farm members for Windows and Cygwin to use more
>feature-enabling options, because in those cases we really need the
>information about which extra features compile and work.)
>
>
I will try. For Windows especially, it's possibly quite a deal of work -
the client is running experimental code that is quite radically
different from the released buildfarm code. Getting it to work with
python, tcl, and openssl will be fun ... at any rate it will not be done
by me for days. If anyone else (Magnus? Dave?) can supply this info for
Windows I'd be glad.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2004-12-07 00:38:37 | Re: branch for 8.0? |
Previous Message | Andrew Dunstan | 2004-12-07 00:15:23 | apparent problem on linux/s390 |