P is for Practical | |
PerlMonks |
Re^3: PAR::Packer/perlbrew confusionby kcott (Archbishop) |
on Nov 29, 2015 at 06:11 UTC ( [id://1148795]=note: print w/replies, xml ) | Need Help?? |
Reading your response, a memory (from quite some time ago) resurfaced of a similar problem I had. Given the length of time that's passed, I won't guarantee my recollection is perfect, but I seem to recall that I had an issue where perlbrew itself was invoking the system perl via the shebang line.
The perlbrew script is installed under the user's home directory. For me:
I manually modified that. I believe I only changed the shebang line (and, thankfully, added comments about what I did). Given the executable part of the script is tiny, here it is in its entirety (minus POD):
I have installed, and successfully used, three more versions of Perl since perl-5.18.1t:
So, at least to date, this tactic has worked well. Perhaps it will for you as well. "... was to trash my system Perl." I understand you did what you did for pragmatic reasons; however, I rather expect this will come back to bite you in the bum. My recommendation would be to reinstall the system perl; although, as I've never had to do this, I'm unable to advise how to go about it. — Ken
In Section
Seekers of Perl Wisdom
|
|