1 files changed, 0 insertions, 63 deletions
diff --git a/chromium/third_party/cygwin/lib/perl5/5.10/Config/Extensions.pm b/chromium/third_party/cygwin/lib/perl5/5.10/Config/Extensions.pm
deleted file mode 100644
index 82fb9e09e89..00000000000
--- a/chromium/third_party/cygwin/lib/perl5/5.10/Config/Extensions.pm
+++ /dev/null
@@ -1,63 +0,0 @@
-package Config::Extensions;
-use strict;
-use vars qw(%Extensions $VERSION @ISA @EXPORT_OK);
-use Config;
-require Exporter;
-
-$VERSION = '0.01';
-@ISA = 'Exporter';
-@EXPORT_OK = '%Extensions';
-
-foreach my $type (qw(static dynamic nonxs)) {
-    foreach (split /\s+/, $Config{$type . '_ext'}) {
-	s!/!::!g;
-	$Extensions{$_} = $type;
-    }
-}
-
-1;
-__END__
-=head1 NAME
-
-Config::Extensions - hash lookup of which core extensions were built.
-
-=head1 SYNOPSIS
-
-    use Config::Extensions '%Extensions';
-    if ($Extensions{PerlIO::via}) {
-        # This perl has PerlIO::via built
-    }
-
-=head1 DESCRIPTION
-
-The Config::Extensions module provides a hash C<%Extensions> containing all
-the core extensions that were enabled for this perl. The hash is keyed by
-extension name, with each entry having one of 3 possible values:
-
-=over 4
-
-=item dynamic
-
-The extension is dynamically linked
-
-=item nonxs
-
-The extension is pure perl, so doesn't need linking to the perl executable
-
-=item static
-
-The extension is statically linked to the perl binary
-
-=back
-
-As all values evaluate to true, a simple C<if> test is good enough to determine
-whether an extension is present.
-
-All the data uses to generate the C<%Extensions> hash is already present in
-the C<Config> module, but not in such a convenient format to quickly reference.
-
-=head1 AUTHOR
-
-Nicholas Clark <nick@ccl4.org>
-
-=cut