package ExtUtils::Mkbootstrap;
-$VERSION = substr q$Revision: 1.13 $, 10;
-# $Date: 1996/09/03 17:04:43 $
+# There's just too much Dynaloader incest here to turn on strict vars.
+use strict 'refs';
+
+use vars qw($VERSION @ISA @EXPORT);
+$VERSION = '1.17';
+
+require Exporter;
+@ISA = ('Exporter');
+@EXPORT = ('&Mkbootstrap');
use Config;
-use Exporter;
-@ISA=('Exporter');
-@EXPORT='&Mkbootstrap';
+
+use vars qw($Verbose);
+
sub Mkbootstrap {
my($baseext, @bsloadlibs)=@_;
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()
=head1 SYNOPSIS
-C<mkbootstrap>
+C<Mkbootstrap>
=head1 DESCRIPTION
Mkbootstrap typically gets called from an extension Makefile.
-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
+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