Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA28084; Tue, 3 Mar 92 11:26:54 -0800
Message-Id: <9203031926.AA28084@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: SCO 3.2.2 port & release 4.0
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Wed, 26 Feb 92 00:48:54 PST."
             <9202260848.AA06562@postgres.Berkeley.EDU> 
Date: Tue, 03 Mar 92 11:26:25 PST

you write:

> at the I'm working on a port of postgres for SCO 3.2.2 for release 3.1.
> Some days ago I read there will be release 4.0 at March. 
> So, my questions are :
> 
> -- Is there an already finished port for SCO (with gcc) ?

There is a fellow (Stephen Williams, williams_stephen_d@ae.ge.com) who
has claimed to have a SCO port mostly done.  I don't believe he was using
gcc.  To get POSTGRES to compile under gcc you have to set flags to make
it run like the standard c compiler (-traditional).

> -- If not, are you interested in having the patches for 3.1 and can
>    you maintain this port ?
>    (most patches relate filenames longer than 14 chars)

We have been telling everyone that we're not interested in supporting
other ports.  We don't really have the manpower to do this (as you might
infer from the delay time for this response).

> -- Or, (arrggghh !!!) should I do the work again for 4.0 and give you
>    the patches ?
> 
> It would be very helpful for porting it to SCO, if you change some
> filenames in release 4.0 to not longer than 14 chars (I can give you the names)

If you send me the names I will shorten them.


Jeff Meredith
mer@postgres.berkeley.edu