enrgyxprt has asked for the wisdom of the Perl Monks concerning the following question:

A series of uninstal, new install (ActiveState) and then Strawberry to try Padre, has left me hunting down
why after using PPM to install something, my package still isn't found...

I see in ther error @INC is C:\perl64... But Perl-v (or -V, I don't remember now) showed @INC C:\perl...

Going to system properties, Advanced, Env Var's
PATH only has C:\perl... paths Not one mention of C:\perl64 in it.
So how is @INC looking in C:\perl64... ?

Replies are listed 'Best First'.
Re: is @inc on windows ALWAYS in env vars?
by Anonymous Monk on Jan 22, 2017 at 16:09 UTC
    What is the full output of perl -V?
[reply]
[d/l]

      fwiw, I uninstalled the 64bit, and that problem looks to have gone, but now must
      perl myperl.pl
      instead of
      myperl.pl

      Guess the file ext .pl was set to the 64bit install... 

      This is perl 5, version 24, subversion 1 (v5.24.1) built for MSWin32-x
+86-multi-thread-64int
(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2017, Larry Wall

Binary build 2402 [401627] provided by ActiveState http://www.ActiveSt
+ate.com
Built Jan  5 2017 01:57:19

Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5 source ki
+t.

Complete documentation for Perl, including FAQ lists, should be found 
+on
this system using "man perl" or "perldoc perl".  If you have access to
+ the
Internet, point your browser at http://www.perl.org/, the Perl Home Pa
+ge

      [download]
[reply]
[d/l]
        That's the output of "perl -v" (lowercase) not "perl -V" (uppercase).
[reply]

Back to Seekers of Perl Wisdom