Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA20326; Wed, 21 Jul 93 04:29:48 -0700
Message-Id: <9307211129.AA20326@postgres.Berkeley.EDU>
From: bidwell@elrond.cs.andrews.edu (Daniel R. Bidwell)
Subject: Re: Postgres on Solaris
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.berkeley.edu
Date: Wed, 21 Jul 1993 07:34:31 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1116      

> 
> 	This is probably a FAQ (although it's not actually in the FAQ), but
> I have only just joined this list and I'm in a bit of a rush... apologies
> to all if I'm stirring up old issues.
> 
> 	The subject sums it up - all our disk and horsepower are tied up in
> a Sun running Solaris 2.2 and we need Postgres up and running A.S.A.P.  I
> have tried dealing with the object-code compatibility issues mentioned in
> the FAQ before (while trying to port Kyoto Lisp, I think) and I don't want
> to attempt it again.  Is there any easy solution?  Has anyone out there
> succeeded in building Postgres on a SVR4 platform?  Patches, hints...
> 
> 	Please help out.  I really appreciate it...
> 
I have had the same need.  I am currently working on getting it to run
on Solaris 2.1.  I will post when I have it working.  Does anyone have
any SVR4 dynamic loading routines already written?

-- 
Daniel R. Bidwell     bidwell@andrews.edu or Daniel.Bidwell@andrews.edu
Andrews University    Computer Science & Information Systems Department
If two always agree, one of them is unnecesary
"Friends don't let friends do DOS"
