[PATCH] Configure's extension sanity check is too strict

The extension sanity check towards the end of Configure is incorrectly
triggered if you don't have DB_File because of the way the extensions list
is sorted.  This patch fixes it and adds in a relevant comment.

Although I took this from the maintenance snapshot, this patch ought to
apply to bleadperl as well.

 --- perl-19333/Configure	Wed Apr 23 16:08:21 2003
+++ perl-andy/Configure	Fri Apr 25 15:49:56 2003
@@ -20299,8 +20299,17 @@
     ;;
 esac

+# Sanity check:  We require an extension suitable for use with
+# AnyDBM_File, as well as Fcntl and IO.  (Failure to have these
+# should show up as failures in the test suite, but it's helpful to
+# catch them now.) The 'extensions' list is normally sorted
+# alphabetically, so we need to accept either
+#    DB_File ... Fcntl ... IO  ....
+# or something like
+#    Fcntl ... NDBM_File ... IO  ....
 case "$extensions" in
 *"_File "*" Fcntl "*" IO "*) ;;
+*" Fcntl "*"_File "*" IO "*) ;;
 *) echo "WARNING: Extensions DB_File or *DBM_File, Fcntl, and IO not configured." >&4
    echo "WARNING: The Perl you are building will be quite crippled." >& 4
    ;;

-- 
    Andy Dougherty		doughera@lafayette.edu

• [PATCH] Configure's extension sanity check is too strict by Andy Dougherty