in reply to Re^5: Flummoxed by strict.pm
in thread Flummoxed by strict.pm

A glutton for Newbie punishment, you are, BrowserUK

But I appreciate it nonetheless

This for two ways:(Wasn't sure about the space

#! perl

[download]
#!perl

[download]

so, same-o, same-o:

C:\Perl64\bin>en
Can't locate strict.pm in @INC (@INC contains: .) at C:\Perl64\bin\ent
+ities_99.p
l line 2.

C:\Perl64\bin>en
Can't locate strict.pm in @INC (@INC contains: .) at C:\Perl64\bin\ent
+ities_99.p
l line 2.

[download]

Thanks again for your help. It can be 100 questions

Replies are listed 'Best First'.
Re^7: Flummoxed by strict.pm
by BrowserUk (Patriarch) on May 08, 2010 at 00:53 UTC

    The space doesn't matter, the shebang line doesn't do much on Win anyway. But, I was trying to preclude the possibility that you had Cywin installed (which does use the shebang lines) and that was interfering.

    You never answered my question about how you installed your perl. Did you use the .ZIP of the .MSI?

    What do you get from perl -le" print for @INC" (Probably just ., but worth a shot.)

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]

      Thanks, BrowserUK.

      I used the .ZIP

      And you're right:

      C:\Perl64\bin>perl -le" print for @INC"
C:/Perl64/site/lib
C:/Perl64/lib
.

      [download]

      Thanks for your patience. And this thread may have worn out that patience, so I'll understand if this has bored you past the limit

[reply]
[d/l]

        Did you run the reloc_perl command after you unzipped? (Not sure if it would make a difference, but worth at least asking.)

        At this point, it's not my patience that has run out, just my ideas.

        The best I can suggest is that you blow away your current installation and get the .msi version. It's the one I always use and I've never encountered your problem. Doesn't mean it would fix it for you, but...

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]

        When you launch Perl via the .pl association, @INC contains only ".". When you launch Perl via the PATH, it contains the three items it should. You appear to have two Perls installed.

        What do you get from 

        >assoc .pl
.pl=Perl

>ftype Perl
Perl="C:\Perl64\bin\perl.exe" "%1" %*

        [download]

        (Replace "Perl" in the second command with what's right of the "=" in the output of the first.)

        If you don't get the same output, you can fix it using 

        ftype Perl="C:\Perl64\bin\perl.exe" "%1" %*

        [download]

        (Again, replace "Perl" with the appropriate value.)

        Update: Cleanup. Added fix.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom