http://qs1969.pair.com?node_id=460352


in reply to perl -V using weird @INC

Go whack your vendor over the head with a copy of the Camel. It looks as if your perl version was compiled with the /tmp/p561 directory as prefix, hence the compiled in @INC points there. Obviously, the perl binary and modules (including Config.pm) are shipped in a different directory.

Three ways of getting around this are use lib qw(/perl/lib/directory) in your scripts, setting the PERL5LIB environment variable to the correct dir, or running perl with -I (see perlrun for that last one).

CU
Robartes-

Replies are listed 'Best First'.
Re^2: perl -V using weird @INC
by polettix (Vicar) on May 25, 2005 at 15:32 UTC
    There's a fourth way: symlink from /tmp/p561 to the base installation directory (which usually is /usr, but in OP could be ~/some/directory/perl).

    Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')

    Don't fool yourself.

      Of course since most OSen clean /tmp on reboot (and on some /tmp may even be in RAM) you'd want to make sure this was done at system startup time.

      Update: Heh, this is my 1337th writeup. wh00t!

Re^2: perl -V using weird @INC
by dorko (Prior) on May 25, 2005 at 15:57 UTC
    Yup, you hit the nail on the head. That's exactly what happened. They compiled Perl in the /tmp area and shipped it in another set of directories. I added export PERL5LIB=/path/to/perl/lib/perl5/5.6.1 to my .profile and it worked like a charm.

    Now, as to your other suggestion, I'm off to go find a big ol' whacking stick.

    Thanks,

    Brent

    -- Yeah, I'm a Delt.