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: <39FA0654.6C604404@ece.gatech.edu>
Date: Fri, 27 Oct 2000 18:48:52 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: David A Ireland <david AT di-mgt DOT com DOT au>
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: GPF error building Perl 5.6
References: <008701c04005$87adc3a0$e3f48490 AT nsw DOT bigpond DOT net DOT au> <39F9A3B6 DOT AF6A551D AT ece DOT gatech DOT edu> <002301c04064$f1a36b20$e3f48490 AT nsw DOT bigpond DOT net DOT au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

David A Ireland wrote:
> 
> Chuck,
> 
> 1. Apologies for missing your message in the archives. I must admit I
> believed the instructions at the start of the Perl-5.6.0-README that said
> "no patches necessary". I must remember to check version numbers a bit more
> closely next time.

When I wrote the README, we were very excited about finally having a
100% compliant perl.  It never occurred to me that *cygwin* would slide
backwards and break compatibility.  (Cygwin has been very good at
constantly improving, and I forgot the old adage that it's sometimes
necessary to go backwards to make progress).

So, I documented that I used:
   cygwin-inst-20000325.tar.gz
   cygwin1-20000328.dll.gz
But 1.1.1 came out very soon after that, and in the official
*announcement* I said it was compatible with cygwin-1.1.1 or better. 
Not "cygwin-1.1.1 only". Sigh.

> 
> 2. I've reloaded Cygwin since the GPF errors with cygipc and have managed to
> build cygipc successfully from the source this time.
> 
> 3. What options do I use with 'patch' for the Perl patches? I'm still a bit
> fresh to this. It's been nearly 15 years since I last used a Unix machine in
> anger.

cd <perlsrc-top>
patch -p1 < {PATH-TO-PATHCES}/perl.cygwin.patch
patch -p1 < {PATH-TO-PATHCES}/perl.cygwin.patch2
patch -p1 < {PATH-TO-PATHCES}/perl.cygwin.patch3
patch -p1 < {PATH-TO-PATHCES}/perl.cygwin.patch4
..etc..
 
> 4. As for the GPF error when compiling the unpatched Perl, I've attached my
> cygcheck results at the end of this message.

you may need to issue the following (will affect patch behavior and
build behavior)

mount -b --change-cygdrive-prefix

OR set TEMP to a path on a binary-mounted drive:

export TEMP=/tmp

However, I still don't see anything that would cause a GPF.  Wierd.

--Chuck

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