I guess that the version of Module::Build that you have installed is incompatible with the features that this Build.PL requests or something. A look into the Build.PL of DBIx::Class doesn't reveal anything (to me at least) that really requires features of Module::Build that are unavailable in ExtUtils::MakeMaker. I think a blindly ported, untested Makefile.PL like below should work for DBIx::Class as well:
use strict; use ExtUtils::MakeMaker; # See lib/ExtUtils/MakeMaker.pm for details of how to influence # the contents of the Makefile that is written. WriteMakefile( 'NAME' => 'DBIx::Class', 'VERSION_FROM' => 'lib/DBIx/Class.pm', # finds $VERSION 'PREREQ_PM' => { 'Data::Page' => 2.00, 'Scalar::Util' => 0, 'SQL::Abstract' => 1.20, 'SQL::Abstract::Limit' => 0.101, 'Class::C3' => 0.11, 'Storable' => 0, 'Class::Data::Accessor' => 0.01, 'Carp::Clan' => 0, 'DBI' => 1.40, # Required for build 'DBD::SQLite' => 1.11, # Recommended 'Data::UUID' => 0, 'Module::Find' => 0, 'Class::Inspector' => 0, }, # e.g., Module::Name => 1.1 ); 1;
You will have to comment out the modules in the build or recommended sections if you don't want these modules. You might want to report the problem with Module::Build to the Module::Build mailing list or maybe through RT.
In reply to Re: Module::Build, PodParser and no 'file' or 'fh' parameter
by Corion
in thread Module::Build, PodParser and no 'file' or 'fh' parameter
by Brutha
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |