in reply to Interpreter can't find known installed mods (w10)

Run 

perl -V

[download]

(uppercase "V"!) and compare the listed @INC content with what you expect it to be.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Replies are listed 'Best First'.
Re^2: Interpreter can't find known installed mods (w10)
by cormanaz (Deacon) on Aug 13, 2023 at 18:04 UTC 
      @INC:
    C:/Perl64/site/lib/MSWin32-x64-multi-thread
    C:/Perl64/site/lib
    C:/Perl64/lib
    .

    [download]
    Both Date::Manip and URL::Encode are in C:/Perl64/site/lib
[reply]
[d/l]

      I guess that you have another Perl binary lying around, and this other binary is associated with .pl files. This would explain that some modules are found (those have been installed under the other Perl binary as well, or are part of the Core like Storable).

      You can add a line to your script and compare the results of the different invocations:

      print "Perl interpreter: $^X\n";
[reply]
[d/l]

        Or, since it's a compile-time issue 

        BEGIN { print "Perl interpreter: $^X\n"; }

        [download]
[reply]
[d/l]
      For grins, run this code: 
      use strict;
use warnings;

my @paths = grep{/perl/i}split ";", $ENV{PATH};

print "$_\n" for @paths;
__END__
C:\Perl64\site\bin
C:\Perl64\bin

      [download]
      I am also wondering if there is a 32 bit Perl in there somehow?
      That your ASSOC is not set right is an indication that something went wrong in the installation of 64 bit Perl.
[reply]
[d/l]
        This revealed an old install of Strawberry Perl, and ikegami's suggestion revealed that it is associated with the .pl extension. Thanks for the help y'all. I will look into how to change the association.
[reply]

In Section Seekers of Perl Wisdom