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

Re: Call for port reports

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: peter_e(at)gmx(dot)net
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Call for port reports
Date: 2004-12-18 23:24:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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:
> 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
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2004-12-18 23:27:30
Subject: Re: production server down
Previous:From: Bruce MomjianDate: 2004-12-18 22:42:29
Subject: Re: production server down

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