Upgrade to ExtUtils::MakeMaker 6.38

[p5sagit/p5-mst-13.2.git] / lib / ExtUtils / Mkbootstrap.pm

diff --git a/lib/ExtUtils/Mkbootstrap.pm b/lib/ExtUtils/Mkbootstrap.pm
index 1dbcf86..71cc6b7 100644 (file)
--- a/lib/ExtUtils/Mkbootstrap.pm
+++ b/lib/ExtUtils/Mkbootstrap.pm
@@ -1,47 +1,22 @@
 package ExtUtils::Mkbootstrap;
-use Config;
-use Exporter;
-@ISA=('Exporter');
-@EXPORT='&Mkbootstrap';
-$Version=2.0; # just to start somewhere
-
-sub Mkbootstrap {
-
-=head1 NAME
-
-ExtUtils::Mkbootstrap - make a bootstrap file for use by DynaLoader
-
-=head1 SYNOPSIS
-
-C<mkbootstrap>
 
-=head1 DESCRIPTION
+# There's just too much Dynaloader incest here to turn on strict vars.
+use strict 'refs';
 
-Mkbootstrap typically gets called from an extension Makefile.
+use vars qw($VERSION @ISA @EXPORT);
+$VERSION = '6.38';
 
-There is no C<*.bs> file supplied with the extension. Instead a
-C<*_BS> file which has code for the special cases, like posix for
-berkeley db on the NeXT.
+require Exporter;
+@ISA = ('Exporter');
+@EXPORT = ('&Mkbootstrap');
 
-This file will get parsed, and produce a maybe empty
-C<@DynaLoader::dl_resolve_using> array for the current architecture.
-That will be extended by $BSLOADLIBS, which was computed by
-ExtUtils::Liblist::ext(). If this array still is empty, we do nothing,
-else we write a .bs file with an C<@DynaLoader::dl_resolve_using>
-array.
+use Config;
 
-The C<*_BS> file can put some code into the generated C<*.bs> file by
-placing it in C<$bscode>. This is a handy 'escape' mechanism that may
-prove useful in complex situations.
+use vars qw($Verbose);
 
-If @DynaLoader::dl_resolve_using contains C<-L*> or C<-l*> entries then
-Mkbootstrap will automatically add a dl_findfile() call to the
-generated C<*.bs> file.
-
-=cut
 
+sub Mkbootstrap {
     my($baseext, @bsloadlibs)=@_;
-
     @bsloadlibs = grep($_, @bsloadlibs); # strip empty libs
 
     print STDOUT "     bsloadlibs=@bsloadlibs\n" if $Verbose;
@@ -78,10 +53,10 @@ generated C<*.bs> file.
                or die "Unable to open $baseext.bs: $!";
        print STDOUT "Writing $baseext.bs\n";
        print STDOUT "  containing: @all" if $Verbose;
-       print BS "# $baseext DynaLoader bootstrap file for $Config{'osname'} architecture.\n";
+       print BS "# $baseext DynaLoader bootstrap file for $^O architecture.\n";
        print BS "# Do not edit this file, changes will be lost.\n";
        print BS "# This file was automatically generated by the\n";
-       print BS "# Mkbootstrap routine in ExtUtils::Mkbootstrap (v$Version).\n";
+       print BS "# Mkbootstrap routine in ExtUtils::Mkbootstrap (v$VERSION).\n";
        print BS "\@DynaLoader::dl_resolve_using = ";
        # If @all contains names in the form -lxxx or -Lxxx then it's asking for
        # runtime library location so we automatically add a call to dl_findfile()
@@ -97,3 +72,39 @@ generated C<*.bs> file.
     }
 }
 
+1;
+
+__END__
+
+=head1 NAME
+
+ExtUtils::Mkbootstrap - make a bootstrap file for use by DynaLoader
+
+=head1 SYNOPSIS
+
+C<Mkbootstrap>
+
+=head1 DESCRIPTION
+
+Mkbootstrap typically gets called from an extension Makefile.
+
+There is no C<*.bs> file supplied with the extension. Instead, there may
+be a C<*_BS> file which has code for the special cases, like posix for
+berkeley db on the NeXT.
+
+This file will get parsed, and produce a maybe empty
+C<@DynaLoader::dl_resolve_using> array for the current architecture.
+That will be extended by $BSLOADLIBS, which was computed by
+ExtUtils::Liblist::ext(). If this array still is empty, we do nothing,
+else we write a .bs file with an C<@DynaLoader::dl_resolve_using>
+array.
+
+The C<*_BS> file can put some code into the generated C<*.bs> file by
+placing it in C<$bscode>. This is a handy 'escape' mechanism that may
+prove useful in complex situations.
+
+If @DynaLoader::dl_resolve_using contains C<-L*> or C<-l*> entries then
+Mkbootstrap will automatically add a dl_findfile() call to the
+generated C<*.bs> file.
+
+=cut