Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.1.1.5.2.20030507184909.00a74d38@mail.earthlink.net> X-Sender: jeremyhetzler AT mail DOT earthlink DOT net Date: Wed, 07 May 2003 19:00:05 -0700 To: cygwin AT cygwin DOT com From: Jeremy Hetzler Subject: Re: Problems installing Perl packages in Cygwin AND Problems with Activestate perl in Cygwin In-Reply-To: <3EB96820.9010708@physics.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 03:10 PM 5/7/2003 -0500, Charles Plager wrote: >I am running a (fairly) current cygwin install (Installed last month). > >I am trying to either: >1) install LWP and Tk (or any other Perl packages) on Cygwins perl >OR >2) Get activestate Perl (where I have said packages installed already) to >understand how to parce cygwin path names. > >Specifically: > >1) I'm trying to install packages by: >unix> perl -MCPAN -e shell >cpan> install LWP I have a working LWP install on Cygwin. I did it by using cpan to download and untar the packages ("get"), then going into the ~/.cpan/build/foo directories and building "manually". Usually this is just a matter of "perl Makefile.pl; make; make test; make install". You will have to read the modules' READMEs to make sure you have all required dependencies installed. As I recall, LWP needs quite a few other modules which aren't core Perl. They're all easily cpan-gettable, though. One other gotcha: LWP will try to install /usr/bin/HEAD, which will conflict with /usr/bin/head.exe in our flexibly-cased and .exe-semitransparent wonderland. Just rename head.exe to head.exe.bak before the install, or let the HEAD installation fail (it's syntactic sugar for the command line, not needed for Perl code). Tk I can't help you with. >2) The problem is when I've got an Activestate Perl script in >/home/cplager/scripts. For example >unix> cd /home/cplager/scripts >unix> ./script >Can't open perl script "/home/cplager/scripts/script": No such file or >directory You can't teach non-Cygwin Windows apps about Cygwin paths (although you can, as already mentioned, wrap them). Jeremy -- 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/