Yes, these entries shouldn't be there at all. LunarCowgirl, you need to figure out where /home/autumn/perl5/lib/perl5/x86_64-linux and /home/autumn/perl5/lib/perl5 come from, don't think that's perlbrew... | [reply]
[d/l]
[select] |
I've spent an hour looking and googling and I have no idea where they come from. I'm renaming the whole perl5 directory and reinstalling perlbrew to see better how a clean install works.
| [reply] |
Yeah, there are many ways to put stuff in @INC... As ikegami said, environment variables are the first thing to look at (check perl -V). If there is nothing suspicious there, check your ~/.bashrc and/or other files that are executed at shell startup (perhaps your perl command is an alias to perl -I/home/autumn/perl5/lib/perl5 or something). Then I recall there is also sitecustomize.pl... and, of course, any Perl code can just unshift things into @INC.
| [reply]
[d/l]
[select] |
I'm not 100% sure of how perlbrew works, so I don't know if this is how it's supposed to be, but those first two paths in @INC are where all my Perl modules are stored. All those modules are compiled to run with 5.22.0, so, yes, that's the problem. If I rename the directory where those modules are stored, perlbrew works fine, BUT I have no modules in either Perl version. I'm not sure how to fix that problem. I'm going to rename the whole perl5 directory and try a clean install of perlbrew with 5.24.1. I'll see how things work then. | [reply] |