From 898db5740571f1b99fc9eca352f0131b720f2333 Mon Sep 17 00:00:00 2001
From: steve <steve>
Date: Thu, 28 Sep 2006 23:42:14 +0000
Subject: [PATCH]  Describe the preconfigure steps.

---
 autoconf.sh |  2 +-
 mingw.txt   | 21 +++++++++++++++++++++
 2 files changed, 22 insertions(+), 1 deletion(-)

diff --git a/autoconf.sh b/autoconf.sh
index 55cefc919..6bd1ef86b 100644
--- a/autoconf.sh
+++ b/autoconf.sh
@@ -12,7 +12,7 @@ autoconf
 for dir in vpip vpi vvp tgt-vvp tgt-edif tgt-fpga libveriuser cadpli
 do
     echo "Autoconf in $dir..."
-    ( cd ./$dir ; autoconf --include=.. )
+    ( cd ./$dir ; autoconf -f --include=.. )
 done
 
 echo "Precompiling lexor_keyword.gperf"
diff --git a/mingw.txt b/mingw.txt
index cb68297c8..bf205ac78 100644
--- a/mingw.txt
+++ b/mingw.txt
@@ -184,6 +184,27 @@ where we will work from now on.
       makefiles included in the source get confused by white space in
       directory names.
 
+* Preconfigure Icarus Verilog (Not normally needed)
+
+Under certain cases, you may need to "preconfigure" the Icarus Verilog
+source tree. You should only need to do this if you are getting the
+Icarus Verilog source tree from CVS, or you are using an existing
+source tree that you've patched to cause configure.in files to change.
+
+    NOTE: If you are building from a fresh, bundled source tree that
+      you downloaded from an FTP site, then SKIP THIS STEP. Go on to
+      the "Configure Icarus Verilog" step below.
+
+First, remove any autom4te.cache directories that may exist in your
+source tree. These can make a mess of autoconf runs. Then, generate
+configure scripts with this command:
+
+        $ sh autoconf.sh
+
+This script will run the "autoconf" command (part of the msysDTK) to
+generate all the necessary "configure" scripts. This will take a few
+minutes. This should go smoothly.
+
 * Configure Icarus Verilog
 
 Now we are all set to configure and compile Icarus Verilog. Choose a