You, sir, kick all nine kinds of ass! That worked perfectly! The version of perl that was in /usr/bin was 5.005_03, but was a symlink to /etc/alternatives/perl and nowhere else. Dont exactly understand that one, but hey... as long as things are back up and working, who cares?!. Thanks many many times over.
Now, anyone care to elaborate on how exactly @INC and perldoc play together? That doesnt make sense to me... does it (perldoc) call to the perl binary first to get the contents of @INC and thus the path to the modules??
-oakley
Embracing insanity - one twitch at a time >:) | [reply] |
tetsujin 13> /usr/bin/head -3 /usr/bin/perldoc
#!/usr/bin/perl
eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
if 0;
perldoc, oddly enough, is written in perl, and uses
/usr/bin/perl to run itself. So when perl itself has
issues, so does perldoc. Many of the additional tools
that come with perl are written in perl, such as s2p.
You can look through these to see some of Larry and Tom's
coding styles, as well as Other Ways To Do It. | [reply]
[d/l] |
i like when i upgraded, mod_perl and apache broke. this, after i spent about a month trying to make php and mod_perl work together (finally got it to go). bah. | [reply] |
