Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <429E91F0.8050504@tlinx.org>
Date: Wed, 01 Jun 2005 21:58:24 -0700
From: Linda W <cygwin AT tlinx DOT org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
CC: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: How to install perl modules?
References: <429459BF DOT 7070803 AT ieee DOT org> <20050526065141 DOT GB988 AT home> <42962D86 DOT 1030409 AT familiehaase DOT de>
In-Reply-To: <42962D86.1030409@familiehaase.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

FYI -- I discovered the cause of a problem I had in manipulating the
Registry.  There is a bug in the Win32 Registry manipulation routines.
Both TieRegistry and the original Registry interface apparently
 use an older interface -- something like (?), libcalls ending with "A"
where new ones end with "W". The "A" interface was for 8-bit characters.
The "W" interface works with the 16-bit characters in the registry.

While it was thought this might have been due to "bogus" registry entries,
according to the MS registry documentation, the only illegal character
in a registry "name" is "\". This causes perl to fail when manipulating
some binary key- & value- names.

I don't know which other routines still use the older 8-bit character
calls, but there may be similar problems if they use the older
interface.  Note that these modules are broken in the ASPN version
of perl as well.



Gerrit P. Haase wrote:

> George wrote:
>
>> 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.
>
>
> There is an up to date version of libwin32 as well as Win32CORE included
> in the perl distributed, it *should* be possible to build some (not all)
> of the Win32 modules, though I have not tried to build much of them.
> Just try one or another if it is not already included with libwin32.
>
>
> 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/