Call for port reports

Started by Peter Eisentrautabout 21 years ago16 messages
#1Peter Eisentraut
peter_e@gmx.net

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/

#2Andrew Dunstan
andrew@dunslane.net
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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

#3Bruce Momjian
pgman@candle.pha.pa.us
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
#4Marc G. Fournier
scrappy@postgresql.org
In reply to: Bruce Momjian (#3)
Re: Call for port reports

======================
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@hub.org Yahoo!: yscrappy ICQ: 7615664

#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andrew Dunstan (#2)
Re: Call for port reports

Andrew Dunstan <andrew@dunslane.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

#6Andrew Dunstan
andrew@dunslane.net
In reply to: Tom Lane (#5)
Re: Call for port reports

Tom Lane said:

Andrew Dunstan <andrew@dunslane.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

#7Dave Page
dpage@vale-housing.co.uk
In reply to: Andrew Dunstan (#6)
Re: Call for port reports

-----Original Message-----
From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of
Peter Eisentraut
Sent: 07 December 2004 00:01
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] 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

All tests passed on Win32 (including a make installcheck in /contrib).
*However*, note that PAM, Kerberos and pthreads do not (yet) work on
Windows and were therefore excluded.

SELECT version():

"PostgreSQL 8.0.0rc1 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.3.1 (mingw special 20030804-1)"

uname -a:

MINGW32_NT-5.1 PC30 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown

Regards, Dave

#8Andrew Rawnsley
ronz@ravensfield.com
In reply to: Dave Page (#7)
Re: Call for port reports

smallmouth:~/tmp ronz$ uname -a
Darwin smallmouth.local 7.5.0 Darwin Kernel Version 7.5.0: Thu Aug 5
19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC Power
Macintosh powerpc

(or OS X 10.3.5)

./configure --prefix=/Users/ronz/tmp/pgsql8 --enable-thread-safety
--with-tcl --with-perl --with-python --with-krb5 --with-pam
-with-openssl --with-libs=/sw/lib --with-includes=/sw/include

all 96 tests passed

[local]:template1=# select version();
version
------------------------------------------------------------------------
----------------------------------------------------
PostgreSQL 8.0.0rc1 on powerpc-apple-darwin7.5.0, compiled by GCC gcc
(GCC) 3.3 20030304 (Apple Computer, Inc. build 1495)

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

Andrew Rawnsley
President
The Ravensfield Digital Resource Group, Ltd.
(740) 587-0114
www.ravensfield.com

#9Bort, Paul
pbort@tmwsystems.com
In reply to: Andrew Rawnsley (#8)
Re: Call for port reports

Port report for Gentoo (www.gentoo.org) Linux: No errors.

uname -a:
Linux imgvmhost 2.4.26-gentoo-r3 #1 Tue Sep 7 14:20:02 EDT 2004 i686
Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux

gcc -v:
gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)

configure:
./configure --prefix=$mypg --enable-thread-safety --with-tcl --with-perl
--with-python --with-krb5 --with-pam -with-openssl

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

version:
template1=# select version();
version

----------------------------------------------------------------------------
--------------------------------------------------------
PostgreSQL 8.0.0rc1 on i686-pc-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)

(If there are other combinations of options anyone would like me to try,
just let me know. I don't know which combinations are interesting, since the
defaults work for my application.)

#10Kenneth Marshall
ktm@it.is.rice.edu
In reply to: Bort, Paul (#9)
Re: Call for port reports

Port report for Solaris 8: No errors.

uname -a:
SunOS sunos58.build 5.8 Generic_117350-11 sun4u sparc SUNW,UltraAX-i2

gcc -v:
Reading specs from /gcc-3.4.0/sunos5/bin/../lib/gcc/sparc-sun-solaris2.8/3.4.0/specs
Configured with: /gcc-3.4.0/src/dist/configure --prefix=/usr/site/gcc-3.4.0 --enable-shared --with-cpu=v9
Thread model: posix
gcc version 3.4.0

configure:
./configure --prefix=/usr/site/pg800rc1 --enable-thread-safety --with-tcl
--with-perl --with-python --with-krb5 --with-openssl

CFLAGS:
-O3 -fno-sched-interblock

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

version:
postgresql-8.0.0rc1

Port report for Redhat Enterprise 3: No errors.

uname -a:
Linux rhel3 2.4.21-15.EL #1 Thu Apr 22 00:27:41 EDT 2004 i686 i686 i386 GNU/Linux

gcc -v:
Reading specs from /gcc-3.4.0/rhel3/bin/../lib/gcc/i686-pc-linux-gnu/3.4.0/specs
Configured with: /gcc-3.4.0/src/dist/configure --prefix=/usr/site/gcc-3.4.0 --enable-shared --with-tune=pentium3 --with-arch=i686 : (reconfigured) /build/gcc-3.4.0/src/dist/configure --prefix=/usr/site/gcc-3.4.0 --enable-shared --with-tune=pentium3 --with-arch=i686
Thread model: posix
gcc version 3.4.0

configure:
./configure --prefix=/usr/site/pg800rc1 --enable-thread-safety --with-tcl
--with-perl --with-python --with-krb5 --with-openssl

CFLAGS:
-O3

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

version:
postgresql-8.0.0rc1

Port report for Redhat 9: No errors.

uname -a:
Linux redhat9.build 2.4.20-31.9 #1 Fri Jun 25 16:52:01 CDT 2004 i686 i686 i386 Gx

gcc -v:
Reading specs from /opt/opt.CORE/gcc-3.4.0/redhat9/bin/../lib/gcc/i686-pc-linux-gnu/3.4.0/specs
Configured with: /build/gcc-3.4.0/src/dist/configure --prefix=/usr/site/gcc-3.4.0 --enable-shared --with-tune=pentium3 --with-arch=i686
Thread model: posix
gcc version 3.4.0

configure:
./configure --prefix=/usr/site/pg800rc1 --enable-thread-safety --with-tcl
--with-perl --with-python --with-krb5 --with-openssl

CFLAGS:
-O3

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

version:
postgresql-8.0.0rc1

It would be nice if the regression tests actually executed
a select version(); and logged the results in the regression
test.

Ken

#11Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

Peter Eisentraut <peter_e@gmx.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

#12Andrew Dunstan
andrew@dunslane.net
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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

#13Patrick B Kelly
pbk@patrickbkelly.org
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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

#14Travis P
twp@castle.fastmail.fm
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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

#15Tatsuo Ishii
t-ishii@sra.co.jp
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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

Show quoted text

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

#16Oliver Jowett
oliver@opencloud.com
In reply to: Peter Eisentraut (#1)
Re: Call for port reports

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