Support a config.arch file, similar to config.over,

but loaded just before it.

p4raw-id: //depot/perl@12851

2 files changed, 19 insertions, 7 deletions

diff --git a/Configure b/Configure
index 873aecba86..ce5edd6a59 100755
--- a/Configure
+++ b/Configure
@@ -20,7 +20,7 @@
 
 # $Id: Head.U,v 3.0.1.9 1997/02/28 15:02:09 ram Exp $
 #
-# Generated on Thu Oct 25 22:43:09 EET DST 2001 [metaconfig 3.0 PL70]
+# Generated on Mon Nov  5 17:50:04 EET 2001 [metaconfig 3.0 PL70]
 # (with additional metaconfig patches by perlbug@perl.org)
 
 cat >c1$$ <<EOF
@@ -16621,6 +16621,12 @@ if test -d ../UU; then
 	cd ..
 fi
 
+: configuration may be patched via a 'config.arch' file
+if $test -f config.arch; then
+	echo "I see a config.arch file, loading it."
+	. ./config.arch
+fi
+
 : configuration may be patched via a 'config.over' file
 if $test -f config.over; then
 	echo " "
diff --git a/INSTALL b/INSTALL
index a9c673fbf8..1ca2322684 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1315,12 +1315,18 @@ You will then have to rebuild by running
 	make depend
 	make
 
-=item config.over
-
-You can also supply a shell script config.over to over-ride Configure's
-guesses.  It will get loaded up at the very end, just before config.sh
-is created.  You have to be careful with this, however, as Configure
-does no checking that your changes make sense.
+=item config.over and config.arch
+
+You can also supply a shell script config.over to over-ride
+Configure's guesses.  It will get loaded up at the very end, just
+before config.sh is created.  You have to be careful with this,
+however, as Configure does no checking that your changes make sense.
+This file is usually good for site-specific customizations.
+
+There is also another file that, if it exists, is loaded before the
+config.over, called config.arch.  This file is intended to be per
+architecture, not per site, and usually it's the architecture-specific
+hints file that creates the config.arch.
 
 =item config.h