locked_user sundialsvc4 has asked for the wisdom of the Perl Monks concerning the following question:

I've posted this before but if an answer was given I missed it...

(“Many thanks to the Monks who, in their replies to this post, pointed me to my original post, which I really couldn't find...” he said humbly, gripping his alms-bowl now quite tightly...)

On a shared-host system with Perl 5.6.1 (which I can't change), YAML-0.66 “installs” but then flunks its tests. (I am openly suspicious that the root cause of the problem is a missing pre-requisite.)

The test-messages fail with such messages (e.g. in 02-basic-test) as: Bizarre copy of ARRAY in return... or, (this quite frequently...) Use of uninitialized value in eval "string" at lib/YAML/Types.pm line 126...

Does this “ring any bells” with anyone? It's not a new problem, but I'm just not sure how to address it.

P.S. YAML::Syck installs okay.

(As you'll see from the replies-thread, here and over-there, the requisite-modules mentioned are loaded. Basically, the upshot seems to be that YAML is shown to fail quite consistently in CPANTS tests which used Perl 5.6, even though that's the “official” version-requirement and it is what I have available to me here. But the monks also pointed-out that YAML::Syck is much faster anyhow. Since I cannot control the Perl version ... just about everything about this host seems to be very behind the times ... maybe this will point me to a work-around. Many thanks.)

(And of course, it did... Finding that YAML::Syck installed properly and runs fast, it was a simple trick to get CPAN to use it:   o conf yaml_module YAML::Syck  then: o conf commit.)

Replies are listed 'Best First'.
Re: Trouble installing YAML? (Perl 5.6)
by ikegami (Patriarch) on Nov 28, 2007 at 20:48 UTC
Re: Trouble installing YAML? (Perl 5.6)
by jettero (Monsignor) on Nov 28, 2007 at 20:47 UTC

    It may simply require a more modern perl but not mention it in the Makefile.PL or Build.PL ...

    IMO, that's a bug worth posting on rt cpan. But the best bugfix you're likely to get is a use 5.008008 in the YAML.pm.

    -Paul