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 Date: Wed, 25 May 2005 23:51:41 -0700 From: George To: Cygwin List Subject: Re: How to install perl modules? Message-ID: <20050526065141.GB988@home> Reply-To: George Mail-Followup-To: Cygwin List References: <429459BF DOT 7070803 AT ieee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <429459BF.7070803@ieee.org> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes On Wed, May 25, 2005 at 11:55:59AM +0100, Jason Pearce wrote: > Yes, use the CPAN module as Brian suggests. Just make sure environment > variable PERLIO is unset when using -MCPAN, otherwise it will fail. (You > might set this to CRLF for DOS compatibility purposes). > Also be aware that you may have trouble building some modules that use C > code and have not been ported to Cygwin, mainly OS modules like WIN32. > Straight Perl modules should just work out of the box, and CPAN will get > all pre-requisites for you too. You'll never want ppm again! Sorry to go off on a slight tangent here, but is there any documentation anywhere that describe which Win32 modules are problematic, as it's most likely that for Cygwin users the Win32 modules are of particular interest, no? And installing both Cygwin's Perl and ActiveState's distribution can offer a less than satisfactory solution as it presents its own set of problems. -- George -- 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/