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:	<008501c48db8$4b9e7030$78d96f83@robinson.cam.ac.uk>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"linda w" <cygwin AT tlinx DOT org>, <cygwin AT cygwin DOT com>
References:	<413144A1 DOT 3060900 AT tlinx DOT org>
Subject:	Re: understanding effects of moving addons from site_perl to vendor_perl
Date:	Sun, 29 Aug 2004 12:06:49 +0100
MIME-Version:	1.0
X-Cam-ScannerInfo:	http://www.cam.ac.uk/cs/email/scanner/
X-Cam-AntiVirus:	No virus found
X-Cam-SpamDetails:	Not scanned
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

linda w wrote:
> It's been a few weeks since I've used perl on my Win machine, but
> noticed an error message about inability to find Win32.pm in my path
> just for starting up perl.
>
> It turned out in my env, I had one of the lib dirs set to
> /usr/local/lib/perl/5.8
> and had it autoloading (not quite sure why at this point) the Win32.pm
> module with "PERL5OPT=-MWin32".
>
> Looking for Win32.pm, I find 3 copies and a 4th name-related copy:
>
> /lib/perl5/5.8.5/ExtUtils/MM_Win32.pm
> /lib/perl5/5.8.5/File/Spec/Win32.pm
> /usr/local/lib/perl/5.8/URI/file/Win32.pm

These are entirely unrelated modules which just happen to contain Win32 in 
their name.

> /lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int/Win32.pm

This is the Win32 module.

> Assuming I wanted to have the same autoload procedure in effect working,
> what directory should be included?

/lib/perl5/site_perl/5.8.2/

> One problem I see on my system seems to be that the perl distro's INC
> path doesn't seem to include the 5.8.2 version files:
>
> Can't locate Win32.pm in @INC (@INC contains:
> /usr/lib/perl5/5.8.5/cygwin-thread
> -multi-64int /usr/lib/perl5/5.8.5
> /usr/lib/perl5/site_perl/5.8.5/cygwin-thread-m
> ulti-64int /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl
> 5/vendor_perl/5.8.5/cygwin-thread-multi-64int
> /usr/lib/perl5/vendor_perl/5.8.5 /
> usr/lib/perl5/vendor_perl .).
> BEGIN failed--compilation aborted.

Interesting. My FC2 linux boxes include all paths back to 5.8.0
My SuSE 9.1 box only includes a single versioned path.

I don't know enough about perl internals to say why this is.

> Shouldn't the perl library and perl interpreter be at the same version?

Win32 is a seperate package (perl-libwin32).

> Is this a mistake or is the library "behind" the interpreter?  I didn't
> choose "experimental" releases, so I would have expected stuff in the main
> line to work together, is this just happenstance?

It's essentially a lack of planning/coordination between the perl and 
perl-libwin32 maintainers.

Max.


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

- Raw text -