Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3975ED0C.2CAA68D5@cascadepg.com>
Date: Wed, 19 Jul 2000 11:01:48 -0700
From: Dan Rosner <rosner AT cascadepg DOT com>
Reply-To: rosner AT cascadepg DOT com
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sources DOT redhat DOT com
Subject: Compiling Postgresql on latest cygwin - 2 questions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings!

Using the "latest" net cygwin, I'm trying to compile Postgresql 7.0.2 
on a windows NT box with sp6a. 

Make works fine until it hits directory backend/access/rtree. 
Then the linker command fails with an error about an unsupported PEI 
architecture pe-i386.

exact linker command: ld -r -o SUBSYS.o rtget.o rtproc.o rtree.o
rtscan.o 
rtstrat.o
exact error message: Unsupported PEI architecture: pe-i386

Target subsys.o is created but 0 length. restarting make ignores the 
described error, but creates the same one in the next directory in 
the sequence.

Question 1:

Does anyone have any idea what is going wrong here?  

Members of the postgresql PORTS list write that there are problems with
some
of the tools in the "latest" cygwin that prevent compilation.  I've 
confirmed this somewhat by scanning the recent cygwin mail archives. 
The 
only current solution I'm aware of is to compile postgresql with an
older version 
of Cygwin.

So my short term solution is to use the old cygwin B20.1 setup to
compile
the latest postgres 7.0.2 binaries.  I then install these binaries
on an NT box with the "latest" net cygwin 1.1.2, and these binaries 
seem to run fine.

Naive Question 2: 

Am I causing trouble by running binaries created with an older version
of cygwin 
on the "latest" net cygwin?

Large thanks for any thoughts about these 2 questions.


Dan

-- 
Dan Rosner
Cascade Programming Group
www.cascadepg.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com