Hello Gisle, thanks for your answer. > ppm initialize install areas from perl's @INC variable when it starts up. > Compare: > > % ppm area list > % perl -le "print for @INC" > % perl -V:sitelib > > What output do these commands give you?
C:\>ppm area list ????????????????????????????????????? ? name ? pkgs ? lib ? ????????????????????????????????????? ? (usr) ? n/a ? D:/usr/site/lib ? ? (usr_2) ? n/a ? D:/usr/lib ? ? site* ? 1 ? C:/Perl/site/lib ? ? perl ? 0 ? C:/Perl/lib ? ????????????????????????????????????? C:\>perl -le "print for @INC" D:/usr/site/lib D:/usr/lib . C:\>perl -V:sitelib sitelib='C:\Perl\site\lib'; > A possible way that @INC could still be set to include C:\Perl\site \lib > is via the PERL5LIB envirionment variable. > C:\>echo %PERL5LIB% %PERL5LIB% (that environment variable is not set, I checked) I ran the command "perl --help" to see what -V flag does, and after reading it, I opened /usr/lib/Config.pm. It had indeed set C:\Perl\\lib for several values, so I changed them. First question: how could that file get changed when it was in a completely different installation folder than the last Perl installation I made? Also, in the same place, there's a Config.pm~ file (including the ~) with the correct values. Renamed by the installer or something else? Well, after changing Config.pm, everything is still the same. The commands I showed before, are still returning the same values. Any ideas? Thanks again. Paco Zarabozo _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
