Mercurial > emacs
changeset 95704:c8c89a82ad33
Clarify why `make bootstrap' sometimes fails.
| author | Alan Mackenzie <acm@muc.de> |
|---|---|
| date | Mon, 09 Jun 2008 08:48:12 +0000 |
| parents | 7df82f24bde6 |
| children | da8d25b7ae00 |
| files | INSTALL.CVS |
| diffstat | 1 files changed, 8 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/INSTALL.CVS Mon Jun 09 08:46:21 2008 +0000 +++ b/INSTALL.CVS Mon Jun 09 08:48:12 2008 +0000 @@ -15,10 +15,15 @@ $ make bootstrap The bootstrap process makes sure all necessary files are rebuilt -before it builds the final Emacs binary. +before it builds the final Emacs binary. Unfortunately, it doesn't +always work when there are stale files from a previous build in the +directory tree. -If 'make bootstrap' fails, it may be necessary to do 'make maintainer-clean' -followed by configure before trying it again. +So if 'make bootstrap' fails, it may be necessary first to do 'make +maintainer-clean' to clear out these stale files. You can then try +again, starting with `./configure'. (Occasionally the loaddefs.el +file gets into a bad state due to changes in the Lisp libraries; this +procedure forces it to be regenerated.) Normally, it is not necessary to use "make bootstrap" after every CVS update. Unless there are problems, we suggest using the following