in reply to Re^2: 2 perl distributions on Windows 7
in thread 2 perl distributions on Windows 7

but any ideas how to force the 5.12 ppm to not know that 5.8 is around?

Clearing the PERL5LIB environment variable should take care of that.
As it stands, I think your 'ppm' is loading perl-5.12.4 - and perl-5.12.4 is finding the 5.8.8 Config.pm (because of the PERL5LIB setting).
That 5.8.8 Config.pm correctly reports that the perl executable is version 5.8.8 ... and you get that mismatch error that you reported.
Remove that PERL5LIB setting and all should be fine.

Cheers,
Rob
  • Comment on Re^3: 2 perl distributions on Windows 7

Replies are listed 'Best First'.
Re^4: 2 perl distributions on Windows 7
by Anonymous Monk on Aug 19, 2011 at 13:39 UTC
    Sorry, I skipped this step in my original post. If I open a new mingw32 GitBash window, carefully pre-pend PATH to include the two perl64 locations and not set PERL5LIB, my results are:
    $ ppm Can't locate ActivePerl/PPM/limited_inc.pm in @INC (@INC contains: /us +r/lib/perl5/5.8.8/msys /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/ +5.8.8/msys /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl .) + at /c/prog/Perl6/bin/ppm line 4. BEGIN failed--compilation aborted at /c/prog/Perl64/bin/ppm line 4.

    This is when I started feeling horrified that ppm, installed with 5.12 dist, somehow finding 5.8 libraries that I personally didn't directly install, in useful directories (/usr/lib/). I can't seem to find the rules for how @INC hardcodes(?) library paths?

    Thanks for your time. I really appreciate it.
    -pamela

      By temporarily hiding the perl v 5.8.8 libs and exe, ppm could work, so I could download the correct missing modules. Now the best-ever script works if I specify the full path to perl v5.12. Good enough for me. Thanks for the help.