X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Harold Fuchs" <harold AT wolfeden DOT demon DOT co DOT uk>
Subject:  Re: perl script dies with The instruction at
Date:  Sun, 24 Dec 2006 23:37:20 -0000
Lines: 48
Message-ID: <emn2vj$ojb$1@sea.gmane.org>
References:  <1166709020 DOT 458a911c4c444 AT easymail-old DOT hol DOT gr> <loom DOT 20061224T230125-71 AT post DOT gmane DOT org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Yitzchak Scott-Thoennes wrote:
> moka writes:
>> Larry Hall wrote:
>>> Don't mix and match perl modules.  If you're using Cygwin's perl,
>>> use modules built and be sure _not_ to use any ActiveState Perl
>>> modules and vice-versa.
>> Well, I did not mean to mix. In fact I think I did not ask cygwin to
>> install perl, but I am  not sure.  I do not find any perl in
>> c:\cygwin\bin
>> There is a perl file directory in c:\cygwin\lib though
>>
>>  I just didn't deinstall Activestate
>> Now  when I do from a DOS prompt, even in a c:\cygwin subdirectory
>> which perl
>> I get back
>> \cygdisk\c\perl\bin\perl
>>
>> which is C:\perl\bin\perl.exe, i.e.  the activestate one
>> Originally I thought this was a path problem, i.e. if I put
>>  c:\perl\bin first in the path, only the activestate perl would be
>> used.
>
> How are you starting your script?  Can you put: print "$^O: $]\n"
> or something at the beginning and verify for sure which perl you are
> using?
>
> If you are accidentally running cygwin's perl and it's loading
> activestate modules, uninstalling the perl packages should help.
>
> If you are running activestate's perl and it is finding some cygwin
> perl modules, that would cause a problem also.  Adding something like:
>  BEGIN { unshift @INC, sub {
>    print join ":", "loading", @_, caller, "\n";
>    return;
>  }; }
> at the beginning of your script, that may help isolate the problem.

At a command prompt (DOS/CMD or cygwin) do "perl -version" (no quotes). Not 
"-v"; spell it out in full. That will tell you, for each shell, which 
version of perl *perl* thinks is running. Then, if you have two different 
ones, remove the one you don't want.

-- 

Harold Fuchs
London, England 




--
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/