From 3038438f167dbacf45bee16834d219225283653b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Johan=20Sundstr=C3=B6m?= <oyasumi@gmail.com>
Date: Mon, 12 Mar 2007 06:07:48 +0100
Subject: [PATCH] Oops; read diffs sloppily. Reinstated docs on configure
--reconfigure.
Rev: README-CVS:1.27
---
README-CVS | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/README-CVS b/README-CVS
index 83a07dd9e3..796ae123e8 100644
--- a/README-CVS
+++ b/README-CVS
@@ -1,4 +1,4 @@
-$Id: README-CVS,v 1.26 2007/03/12 04:54:24 jhs Exp $
+$Id: README-CVS,v 1.27 2007/03/12 05:07:48 jhs Exp $
HOW TO BUILD PIKE FROM CVS
@@ -74,12 +74,11 @@ source Prepare the source tree for compilation without
force_autoconfig Force a build of the configure scripts. This is
useful e.g. if a new module directory is added in
the CVS.
-force_configure Force configure to be run (recursively). If
- you've installed a new library and want Pike to
- detect it, then the simplest way is to remove
- config.cache in the build directory (or perhaps
- just delete the relevant variables in it) and then
- use this target.
+force_configure Force configure to be run (recursively).
+reconfigure Remove the cached results from previous configure
+ runs and rerun configure recursively. If you have
+ installed a new library and want Pike to detect it
+ then the simplest way is to use this target.
dump_modules Dump the Pike modules directly in the build tree.
That makes Pike load faster if it's run directly
from there, e.g. through the bin/pike script (see
--
GitLab