more useful options | |
PerlMonks |
Re: Strawberry Perl NOT running properlyby Don Coyote (Hermit) |
on Apr 19, 2015 at 15:25 UTC ( [id://1123964]=note: print w/replies, xml ) | Need Help?? |
Hello wa5nti and welcome to the monastery. Where to start? There could be many reasons for this occurence, so I can only make suggestions. I was struck by the Non-installation of perldoc in Strawberry occurs when a certain config variable is defined at install time.
Heres a one liner to see if this variable was defined at installation.
Should you find this variable is defined in some way, the simplest method would most likely be to re-install taking care not to install a version dependant version. Other than that there are a huge number of variables, that do not show up in the perl -V invocation. Given the difficulty of being able to run perldoc, you may find a look at some of the path variables in the list lead you somewhere useful.
This will provide a list something along the form of what can be seen here Example Config Variable Listing (note: Example is defined as relating to use in this forum reply, not the code itself). Maybe check libpath variables in this list, and also permissions on the directories the paths indicate. For TMP paths, I usually see a shortname as upper case suffixed with tilde V:\STRAWB~\lib\path\ Pod is included with modules, you can check the scripts directly, and Pod is accessible through online sources CPAN Perl5 Perl is Perl, if none of this helps, maybe consider re-installing Active-State, as it was working for you previously, until you are more familiar with the language. I hope this helps. Local access to all the really useful beginners documentation is essential for a good learning experience. On Review edit: no such thing as facts. Ambiguous error messages yes. For further insight to the problem you can try supplying debug options to perldoc. from perldoc docs perldoc perldoc Having PERLDOCDEBUG set to a positive integer will make perldoc emit even more descriptive output than the "-D" switch does; the higher the number, the more it emits.
In particular when outputting through a pager to the terminal(perldoc default behaviour), Perldoc creates TMP files to construct the output. Using the -d, -T,or -t options may circumnavigate this by directing the output specifically. Worth trying, while you figure out the root of the problem. The -q,-f options require temp files to work, so they will not be useable until your main problem is fixed Why are you re-inventing the wheel? So I can test it goes round!
In Section
Seekers of Perl Wisdom
|
|