I think the problem is in Parse::CPAN::Meta, seems to be a lot of changes here: 

--- Meta.pm    2014-03-04 15:22:05.000000000 -0500
+++ /u01/oracle/Meta.pm    2014-04-10 11:24:46.069085636 -0400
@@ -2,7 +2,7 @@ use 5.008001;
 use strict;
 package Parse::CPAN::Meta;
 # ABSTRACT: Parse META.yml and META.json CPAN metadata files
-our $VERSION = '1.4414'; # VERSION
+our $VERSION = '1.4413'; # VERSION
 
 use Exporter;
 use Carp 'croak';
@@ -13,30 +13,15 @@ our @EXPORT_OK = qw/Load LoadFile/;
 sub load_file {
   my ($class, $filename) = @_;
 
-  my $meta = _slurp($filename);
-
   if ($filename =~ /\.ya?ml$/) {
-    return $class->load_yaml_string($meta);
-  }
-  elsif ($filename =~ /\.json$/) {
-    return $class->load_json_string($meta);
-  }
-  else {
-    $class->load_string($meta); # try to detect yaml/json
+    return $class->load_yaml_string(_slurp($filename));
   }
-}
 
-sub load_string {
-  my ($class, $string) = @_;
-  if ( $string =~ /^---/ ) { # looks like YAML
-    return $class->load_yaml_string($string);
-  }
-  elsif ( $string =~ /^\s*\{/ ) { # looks like JSON
-    return $class->load_json_string($string);
-  }
-  else { # maybe doc-marker-free YAML
-    return $class->load_yaml_string($string);
+  if ($filename =~ /\.json$/) {
+    return $class->load_json_string(_slurp($filename));
   }
+
+  croak("file type cannot be determined by filename");
 }
 
 sub load_yaml_string {
@@ -136,7 +121,7 @@ Parse::CPAN::Meta - Parse META.yml and M
 
 =head1 VERSION
 
-version 1.4414
+version 1.4413
 
 =head1 SYNOPSIS
 
@@ -216,13 +201,6 @@ This method deserializes the given strin
 If the source was UTF-8 encoded, the string must be decoded before ca
+lling
 C<load_json_string>.
 
-=head2 load_string
-
-  my $metadata_structure = Parse::CPAN::Meta->load_string($some_strin
+g);
-
-If you don't know whether a string contains YAML or JSON data, this m
+ethod
-will use some heuristics and guess.  If it can't tell, it assumes YAM
+L.
-
 =head2 yaml_backend
 
   my $backend = Parse::CPAN::Meta->yaml_backend;

[download]

Will see if I can trouble shoot further. Any suggestions appreciated.

In reply to Re^4: Module::Build::XSUtil build problem by jimhallsun
in thread Module::Build::XSUtil build problem by jimhallsun

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.