in reply to @INC is suddenly changed? Not recognizing any of my modules

Most of the paths are hardcoded into the executable. The only reasons they'd disappear is if you're using a different executable of it something is mucking with @INC.

Other paths include those added by env var PERL5LIB, env var PERLLIB, Perl's -I cmd line opt, the lib module or manually.

And then there's the case of paths being present, but not accessible. They could be relative paths and your current directory isn't what you think it is, or it could be a permissions problem.

Replies are listed 'Best First'.
Re^2: @INC is suddenly changed? Not recognizing any of my modules
by adityadennis (Novice) on Sep 06, 2009 at 17:57 UTC
    Setting the ENV variables makes no difference at all. Even if I put the absolute path in a BEGIN block, it still doesn't recognize the module. What sort of permissions problem could there be?
[reply]
      Ok, I figured it out. Turns out /opt/local/bin was no longer in my path for some reason. The clue was when other utilities stopped working too. It's all back to normal now.
[reply]

In Section Seekers of Perl Wisdom