Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-AuthUser: gerrit:koeln.convey.de
Date: Wed, 30 Apr 2003 22:22:19 +0200
From: "Gerrit P. Haase" <gp@familiehaase.de>
Organization: Esse keine toten Tiere
X-Priority: 3 (Normal)
Message-ID: <18897903517.20030430222219@familiehaase.de>
To: "cygwin" <cygwin@cygwin.com>
CC: "Michael Lemke" <lemkemch@t-online.de>
Subject: Re: Perl instabilities
In-Reply-To: <184210111424.20030428230200@familiehaase.de>
References: <UTZVTO32ZY1XWRZV62ZT843WWUQNWUNH.3ead71ec@micha>
 <000801c30db9$8ff11c40$2e5986d9@ellixia>
 <184210111424.20030428230200@familiehaase.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hallo,

> Michael wrote:
>>> I just had the problem when I tried to build perl on VMS.  Threads and
>>> 64bit stuff wouldn't work.  Just a thought.

> Elfyn:
>> Just a WAG, maybe it's down to the 64-int support. Perhaps re-building from
>> source without 64-int might do something...

> Ok, I'll build a version without 65-int support tomorrow, will send
> you a the download URL when ready.

Ok, here it is, I don't know exactely where, but I lost the 65th bit;)
http://anfaenger.de/cygwin/perl/perl-5.8.0-no64bit.tar.bz2
http://anfaenger.de/cygwin/perl/md5sums

Sourcepackage available on request.

Can you try to reproduce the problem with this perl?

Just extract it from the root dir '/', probably it is better to
uninstall previous perl-5.8.0 versions with setup.exe.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

