aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlan Mackenzie2008-06-09 08:48:12 +0000
committerAlan Mackenzie2008-06-09 08:48:12 +0000
commit274559e1125e9a849c6028742cf9cc7d8c4fa18f (patch)
tree91c6fc68d4d3c5358a9ad949d5ddc49296b2e85d
parent294e8689d1009eaaa061efb6d151173d4507811b (diff)
downloademacs-274559e1125e9a849c6028742cf9cc7d8c4fa18f.tar.gz
emacs-274559e1125e9a849c6028742cf9cc7d8c4fa18f.zip
Clarify why `make bootstrap' sometimes fails.
-rw-r--r--INSTALL.CVS13
1 files changed, 9 insertions, 4 deletions
diff --git a/INSTALL.CVS b/INSTALL.CVS
index c2b1df622fd..e21738d505c 100644
--- a/INSTALL.CVS
+++ b/INSTALL.CVS
@@ -15,10 +15,15 @@ instead of just "make":
15 $ make bootstrap 15 $ make bootstrap
16 16
17The bootstrap process makes sure all necessary files are rebuilt 17The bootstrap process makes sure all necessary files are rebuilt
18before it builds the final Emacs binary. 18before it builds the final Emacs binary. Unfortunately, it doesn't
19 19always work when there are stale files from a previous build in the
20If 'make bootstrap' fails, it may be necessary to do 'make maintainer-clean' 20directory tree.
21followed by configure before trying it again. 21
22So if 'make bootstrap' fails, it may be necessary first to do 'make
23maintainer-clean' to clear out these stale files. You can then try
24again, starting with `./configure'. (Occasionally the loaddefs.el
25file gets into a bad state due to changes in the Lisp libraries; this
26procedure forces it to be regenerated.)
22 27
23Normally, it is not necessary to use "make bootstrap" after every CVS 28Normally, it is not necessary to use "make bootstrap" after every CVS
24update. Unless there are problems, we suggest using the following 29update. Unless there are problems, we suggest using the following