Dr Manhattan has asked for the
wisdom of the Perl Monks concerning the following question:

Hi all

I installed Wiktionary::Parser on a Windows7 64bit operating system through ppm. The problem is that I get a error message rigth at the start of my script, even though (I think) the module installed correctly.

When it uses Locale::Codes::Language, is disables imports: use Locale::Codes::Language qw(); and attempts to obtain access to the constants, that would have been imported, by using fully qualified names:

I've never tested this package on a Windows platform, but I'm pretty tickled that it worked as well as it did. I've mainly run the code on various versions of CentOS on perl 5.8 and 5.16 and never ran into any of the above issues.

I pushed a few updates to try to fix some of them but since I can't recreate these errors I'm a bit blind as to whether it'll be effective.

I've never tested this package on a Windows platform, but I'm pretty tickled that it worked as well as it did. I've mainly run the code on various versions of CentOS on perl 5.8 and 5.16 and never ran into any of the above issues.

It is hard to see how the particular coding error I identified as the cause of the OPs immediate problem would be in any way platform specific.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Bareword "Locale::Codes::Language::LOCALE_LANG_ALPHA_3" not allowed wh+ile "strict subs" in use at /home/soeren/perl5/lib/perl5/Wiktionary/P+arser/Language.pm line 49.
Compilation failed in require at /home/soeren/perl5/lib/perl5/Wiktiona+ry/Parser/Section.pm line 8.
BEGIN failed--compilation aborted at /home/soeren/perl5/lib/perl5/Wikt+ionary/Parser/Section.pm line 8.
Compilation failed in require at /home/soeren/perl5/lib/perl5/Wiktiona+ry/Parser/Document.pm line 6.
BEGIN failed--compilation aborted at /home/soeren/perl5/lib/perl5/Wikt+ionary/Parser/Document.pm line 6.
Compilation failed in require at /home/soeren/perl5/lib/perl5/Wiktiona+ry/Parser.pm line 8.
BEGIN failed--compilation aborted at /home/soeren/perl5/lib/perl5/Wikt+ionary/Parser.pm line 8.
Compilation failed in require at test.pl line 2.
BEGIN failed--compilation aborted at test.pl line 2.

OP used PPM, prerequsites are installed via PPM. Why have you scripted a cpan install when running cpan Wiktionary::Parser from the command line will do the same thing?

Also note that OP said he was on Windows 7 64 bit, if they're using 64 bit ActiveState Perl no C compiler or build tools are installed by default, and aren't available on the 64bit platform from PPM. So without them manualling installing all this your suggestion of a cpan installation may fail.

First, Wiktionary::Parser has few dependencies that need to updated before you install the parser.

First, when you "installed Wiktionary::Parser on a Windows7 64bit operating system through ppm", PPM should have resolved and installed all dependencies when it was built on the PPM server (by ActiveState or whomever runs the PPM server).

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

After installing all of Wiktionary::Parser dependencies, I do not get the error message as before, so it seems to have worked.

However when I try to run the script that you posted (I had a look at Wiktionary::Parser documentation and it looks correct), I get a new error message- 'Can't call method "get_derived_terms" on an undefined value at \some\dir\script.pl line 12'. Any ideas?

So the latest version of Wiktionary::Parser (0.11) should have fixed this error. In previous versions, the cpan testers reports for perl 5.14 on a number of platforms were showing the same issue, all of which are passing now. If the root cause was the same then this case should be resolved too.