Well I tried upgrading to the newest Perl 5.14 which is also 64 bit
capable. I discovered that Tk.pm is not yet available from ppm.
So I backed off to 5.12 which says Tk.pm is available on the ppm
web site. For reasons I have not yet figured out, I get timeouts
accessing ppm4.activestate.com.
Just as a slightly off topic question. Since my original question was
answered with a top post, is this acceptable on this list? The guys on
the Fedora lists get all bent out of shape if someone top posts.
There are various references to incompatibilites between pm modules
on 5.6 and 5.14 although I have not gotten far enough (not havimg Tk) to
be sure if any of them affect the local .pm modules in my site.lib. Is there
a summary of what sort of things break between 5.6 and 5.14?
Sorting that out from the release notes is about as effective as ploughing
ahead and just debugging.
Thank you for the help.
Bob
From: Jan Dubois [mailto:j...@activestate.com]
Sent: Friday, January 06, 2012 10:39 AM
To: Styma, Robert E (Robert); perl-win32-users@listserv.ActiveState.com
Subject: RE: Window 7 x64, @inc search question
Your description on how things are looked up sounds correct. You may want to
run `perl -V` to check the list of directories in @INC, and the order in which
they are searched (the order of lib and site/lib has changed between 5.6 and
5.14).
Cheers,
-Jan
From: perl-win32-users-boun...@listserv.activestate.com
[mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Styma,
Robert E (Robert)
Sent: Friday, January 06, 2012 8:30 AM
To: perl-win32-users@listserv.ActiveState.com
Subject: Window 7 x64, @inc search question
Robert E. Styma
I have just joined this mailing list. I am responsible for an
assortment of perl programs which I have inherited and am
testing and adjusting to get them running under a Windows 7 X64
environment.
At the time the code was written we were using Perl 5.6.1.
When I discovered problems, I removed the old Perl and upgraded
to:
ActivePerl-5.14.2.1402-MSWin32-x64-295342.msi
The problem I encountered remained the same.
Here is the deal.
...\Perl\lib has a directory called File which has the file functions.
In the Perl\site\lib we use there is also a directory called File which
includes among other things, File\Recurse.pm. This comes up
as a not found on when run on a Windows 7 x64 machine.
If I copy the Recurse.pm to the ...\Perl\lib it is found.
On Windows XP and Windows 7 x86 the Recurse.pm is found
in the Perl\Site\Lib\File directory and the other appropriate modules
are found in Perl\Lib\File. I only tested this on the Perl 5.6.1 version
since it works.
I suspect the problem is due to
changes in the underlying OS code used to do the search.
I personally think that naming the Perl\Site\Lib folder the same
as a Perl\Lib folder was a poor choice. However, that is what
is there and I want to make sure that this is the expected behavior
before I try to untangle this with changes to the code.
I am looking for confirmation that someone else has seen such behavior
or that this is known to be the way it should work. If what is being done
should work, then I need to figure out what to try next.
Thanks in advance for any suggestions.
Bob Styma
___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
