From 8991a4720cb7976fc5814c9fba10e1bba1b7a70c Mon Sep 17 00:00:00 2001
From: Martin Nilsson <mani@lysator.liu.se>
Date: Wed, 5 Nov 2003 02:47:35 +0100
Subject: [PATCH] Removed CVS statement that has confused at least one
 potential Pike user. Don't mention make depend in the normal build procedure.

Rev: README:1.17
---
 README | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/README b/README
index 4443a83464..a97e78c958 100644
--- a/README
+++ b/README
@@ -13,8 +13,7 @@ pike-request@roxen.com
 HOW TO BUILD PIKE
 
 The top-level makefile (in this directory, not the src directory) has
-all the magic you need to build pike directly from CVS.  Just type
-'make'.
+all the magic you need to build Pike.  Just type 'make'.
 
 You will need autoconf, gnu m4, bison, a C compiler and the GMP
 library. You probably also want to use GNU make and libz.
@@ -70,24 +69,21 @@ yourself, try the Old instructions:
    modules.  If the configure script doesn't find them, Pike will
    still compile, but without those modules.
 
-4) Run 'make depend'
-   This updates all the Makefile.in files in the source dir to contain
-   the correct dependencies
-
-5) If needed, edit config.h and Makefile to suit your purposes.  I've
+4) If needed, edit config.h and Makefile to suit your purposes.  I've
    tried to make it so that you don't have to change config.h or
    Makefile at all.  If you need to do what you consider 'unnecessary
    changes' then mail us and we'll try to fit it into configure.  If
    possible, use gnu make, gcc, gnu sed and bison
 
-6) Run 'make'
+5) Run 'make'
    This builds pike.
 
-7) Optionally, run 'make verify' to check that the compiled driver
+6) Optionally, run 'make verify' to check that the compiled driver
    works as it should (might be a good idea).  This will take a little
    time and use quite a lot of memory, because the test program is
    quite large.  If everything works out fine no extra messages are
-   written.
+   written. You will need GNU m4 for this stage to generate the test
+   case files.
 
 8) If you want to install Pike, write 'make install'.  This will put
    your pike in <prefix>/pike/<version>/. This way, you can install
@@ -105,6 +101,8 @@ IF IT DOESN'T WORK:
 
  o Try again.
 
+ o Try running 'make depend'.
+
  o Your sh might be too buggy to run ./configure. (This is the case on
    A/UX) Try using bash, zsh or possibly ksh.  To use bash, first run
    /bin/sh and
-- 
GitLab