Restore your system version of Perl, and don't mess with it outside of the standard OS-level upgrades. There are OS-level applications that depend upon a certain base configuration to accomplish what they do.
Instead, use something like perlbrew to manage a second (third, fourth...) Perl installation that you use for development.
If you use TimeMachine, you should be able to restore the directories in the error messages to a certain state, but that is not something I would look forward to doing by hand.
Also, please add <code>...</code> tags around your code, data, and error messages to make it easier to read. OP updated with code tags. Thanks.
Update: Glossed over the majority of the unformatted text as error text. OP has used the perlbrew route and is asking a different question.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||