Call for port reports

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

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.)

If your system provides multiple compilers (for example, a vendor
compiler and GCC), test with all of them. Call configure as
follows: ./configure CC=/foo/cc --prefix=...

If your system has multiple compilation modes, such as 32 bit and 64
bit, it may be worth trying both.

Report the output of SELECT version(); as well as a "common name" of the
operating system under which it can be listed (e.g., the distributor,
in case of a Linux-based system).

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

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

Sorry, here is select version();

PostgreSQL 8.0.0rc1 on i386-pc-bsdi4.3.1, compiled by GCC 2.95.3

---------------------------------------------------------------------------

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
>
> 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.)
>
> If your system provides multiple compilers (for example, a vendor
> compiler and GCC), test with all of them. Call configure as
> follows: ./configure CC=/foo/cc --prefix=...
>
> If your system has multiple compilation modes, such as 32 bit and 64
> bit, it may be worth trying both.
>
> Report the output of SELECT version(); as well as a "common name" of the
> operating system under which it can be listed (e.g., the distributor,
> in case of a Linux-based system).
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

======================
All 96 tests passed.
======================

version
----------------------------------------------------------------------------------------------------
PostgreSQL 8.0.0rc1 on i386-unknown-freebsd5.3, compiled by GCC gcc (GCC) 3.4.2 [FreeBSD] 20040728
(1 row)

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Peter Eisentraut wrote:
>> ./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.

There is a difference, which is that on some (most?) platforms the
latter sequence will involve "make check" invoking the libpq shared
library that was installed by the previous iteration of "make install".

I'm not sure that this matters a whole lot for the buildfarm, since at
worst it would result in failures for one test cycle when libpq.so
changes incompatibly. But it's important to realize what you are testing.

regards, tom lane

Tom Lane said:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Peter Eisentraut wrote:
>>> ./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.
>
> There is a difference, which is that on some (most?) platforms the
> latter sequence will involve "make check" invoking the libpq shared
> library that was installed by the previous iteration of "make install".
>
> I'm not sure that this matters a whole lot for the buildfarm, since at
> worst it would result in failures for one test cycle when libpq.so
> changes incompatibly. But it's important to realize what you are
> testing.
>

The script installs to a non-standard location ( <buildroot>/<branch>/inst )
and removes the installation at the end of each run. In fact, it refuses to
run if this directory exists when the run starts, precisely so we don't get
clobbered by previous runs.

Also, note that since it stops on the first step that fails, the failure
would persist rather than lasting one cycle, had we not prevented it in the
first place.

cheers

andrew

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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
> 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.

All regression tests pass on all seven architectures supported by
Red Hat Enterprise Linux 3AS:
i386 generic Intel
ia64 Itanium
x86_64 AMD
ppc IBM pSeries
ppc64 pSeries 64-bit
s390 IBM zSeries
s390x zSeries 64-bit

I did not test --with-tcl --with-python --with-krb5 --with-pam
--with-openssl, for lack of installed packages, but since this is
basically Linux I doubt there's much to be learned there. (If there is
any problem with building with those packages added, I'll find out when
I try to make Red Hat's RPMs ;-))

PostgreSQL 8.0.0rc1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-47)
PostgreSQL 8.0.0rc1 on ia64-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
PostgreSQL 8.0.0rc1 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-34)
PostgreSQL 8.0.0rc1 on powerpc-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-38)
PostgreSQL 8.0.0rc1 on powerpc64-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-38)
PostgreSQL 8.0.0rc1 on s390-ibm-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-47)
PostgreSQL 8.0.0rc1 on s390x-ibm-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-47)

regards, tom lane

Peter Eisentraut wrote:

> 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
>
>(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 have successfully added --with-perl --with-python --with-openssl to
the buildfarm cygwin member.

Currently --with-tcl is giving me link problems.

I'm not sure how relevant krb5 and pam are - I suspect not.

cheers

andrew

./configure \
--prefix=/usr/local/pgsql/8.0rc1 \
--enable-thread-safety \
--with-tcl \
--with-perl \
--with-python \
--with-krb5 \
--with-pam \
--with-openssl \
--with-includes=/sw/include/ \
--with-libraries=/sw/lib

make check
======================
All 96 tests passed.
======================

test8=# select version() ;
version
------------------------------------------------------------------------
----------------------------------------------------
PostgreSQL 8.0.0rc1 on powerpc-apple-darwin7.6.0, compiled by GCC gcc
(GCC) 3.3 20030304 (Apple Computer, Inc. build 1666)
(1 row)

On Dec 6, 2004, at 7:00 PM, 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
>
> 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.)
>
> If your system provides multiple compilers (for example, a vendor
> compiler and GCC), test with all of them. Call configure as
> follows: ./configure CC=/foo/cc --prefix=...
>
> If your system has multiple compilation modes, such as 32 bit and 64
> bit, it may be worth trying both.
>
> Report the output of SELECT version(); as well as a "common name" of
> the
> operating system under which it can be listed (e.g., the distributor,
> in case of a Linux-based system).
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>
Patrick B. Kelly
----------------------------------------------------------------------
v: 484.557.0646 http://patrickbkelly.org

I tested with what dependencies were already available. Unfortunately,
even --with-perl couldn't be used because the libraries are apparently
non-shared (or so the build process reported).

======================================
AIX 5.1, 32-bit, four Power4 processors,

# SELECT version();
PostgreSQL 8.0.0rc1 on powerpc-ibm-aix5.1.0.0, compiled by /usr/bin/cc_r

./configure \
CC=/usr/bin/cc_r \
CFLAGS='-qmaxmem=-1' \
--prefix=SOMEWHERE \
--enable-thread-safety \
--with-openssl \

make
make install
make check

All 96 tests passed.
======================================

======================================
AIX 5.1, 64-bit, four Power4 processors,

# SELECT version();
PostgreSQL 8.0.0rc1 on powerpc-ibm-aix5.1.0.0, compiled by /usr/bin/cc_r

export OBJECT_MODE=64

./configure \
CC=/usr/bin/cc_r \
CFLAGS='-qmaxmem=-1 -q64' \
--prefix=SOMEWHERE \
--enable-thread-safety \
--without-readline \
--without-zlib

make
make install
make check

All 96 tests passed.
======================================

Has anybody tried Solaris8 or 9/ADM64(SUN Fire v40 for example) combo?
I personally don't have access to this platform, but am interested in
someone else has already tried.
--
Tatsuo Ishii

> 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
>
> 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.)
>
> If your system provides multiple compilers (for example, a vendor
> compiler and GCC), test with all of them. Call configure as
> follows: ./configure CC=/foo/cc --prefix=...
>
> If your system has multiple compilation modes, such as 32 bit and 64
> bit, it may be worth trying both.
>
> Report the output of SELECT version(); as well as a "common name" of the
> operating system under which it can be listed (e.g., the distributor,
> in case of a Linux-based system).
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

8.0.0rc1 builds and passes 'make check' on Gentoo Linux (amd64) with the
dependencies I have to hand (no tcl or kerberos):

$ ./configure --prefix=/home/oliver/pg/8.0.0rc1 --with-pgport=5800
-enable-thread-safety --with-perl --with-python --with-pam -with-openssl

$ uname -a
Linux extrashiny 2.6.9-gentoo-r3-patched #3 Sun Nov 14 15:18:33 NZDT
2004 x86_64 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux

$ 8.0.0rc1/bin/psql template1 -t -c 'select version()'
PostgreSQL 8.0.0rc1 on x86_64-unknown-linux-gnu, compiled by GCC gcc
(GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)

-O