Re: Strawberry Perl NOT running properly

[Don Coyote]

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 fact that your installation was attempting to install the perldoc program. In my experience Strawberry auto installs this. I find the documentation an inextricable part of the language and its distributions.

Non-installation of perldoc in Strawberry occurs when a certain config variable is defined at install time.

=item C<versiononly>

From F<versiononly.U>:

If set, this symbol indicates that only the version-specific
components of a perl installation should be installed.
This may be useful for making a test installation of a new
version without disturbing the existing installation.
Setting versiononly is equivalent to setting installperl's -v option.

In particular, the non-versioned scripts and programs such as
a2p, c2ph, h2xs, pod2*, and perldoc are not installed
(see C<INSTALL> for a more complete list). Nor are the man
pages installed.
Usually, this is undef.

Heres a one liner to see if this variable was defined at installation.

windos% perl -Mv5.20 -Mstrict -MConfig -w -e "say $Config{versiononly}
+"

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.

#!perl 

use 5.20;
use strict;
use warnings;
use Config qw/config_sh/;

open my $fh, '>', '.\configlist.txt' or die $!;
print {$fh} config_sh(); 
close $fh;

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.

windos% perldoc -D   # or
windos% set PERLDOCDEBUG=9  # 0..9

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!}