commit - 15b5e1a6eb608f3a5c599071ccd1e654d7428479
commit + 23a28fa3364fb2e6f1ab52cce21822d1ac7cf9fe
blob - 81e881f8537dcf7606c9d46f638b321ddbccf92c
blob + e04b27063ee5c79fbdac1793b855fc263cded55b
--- INSTALL
+++ INSTALL
@@ -46,6 +46,7 @@ files (using a distribution archive or CVS) is as foll
   3) make
   4) make install
 
+
 1): "autogen.sh"
 
 The first step, autogen.sh, is only necessary if the configure-script isn't
@@ -56,12 +57,14 @@ This step is therefore only interesting for developper
 
 autogen.sh produces the Makefile.in's, which are necessary for the configure
 script itself, and some more files for make. To run autogen.sh you'll need
-GNU autoconf and GNU automake (in recent versions!).
+GNU autoconf and GNU automake (use recent versions! autoconf 2.53 and
+automake 1.6.1 are known to work).
 
 Again: "end users" do not need this step!
 
-4): "./configure"
 
+2): "./configure"
+
 The configure-script is used to detect local system dependancies.
 
 In the perfect case, configure should recognize all needed libraries, header
@@ -72,13 +75,15 @@ In addition, you can pass some command line options to
 and/or disable some features of ngIRCd. All these options are shown using
 "./configure --help", too.
 
-5): "make"
 
+3): "make"
+
 The make command uses the Makefiles produced by configure and compiles the
 ngIRCd daemon.
 
-6): "make install"
 
+4): "make install"
+
 Use "make install" to install the server and a sample configuration file on
 the local system. Normally, root privileges are necessary to complete this
 step. If there is already an older configuration file present, it won't be
@@ -149,4 +154,4 @@ number. In both cases the server exits after the outpu
 
 
 -- 
-$Id: INSTALL,v 1.11 2003/03/07 14:45:10 alex Exp $
+$Id: INSTALL,v 1.12 2003/03/08 12:34:55 alex Exp $