Mercurial > emacs
comparison INSTALL.CVS @ 95704:c8c89a82ad33
Clarify why `make bootstrap' sometimes fails.
| author | Alan Mackenzie <acm@muc.de> |
|---|---|
| date | Mon, 09 Jun 2008 08:48:12 +0000 |
| parents | 18c9a69d751f |
| children | 7bf8d633ec50 |
comparison
equal
deleted
inserted
replaced
| 95703:7df82f24bde6 | 95704:c8c89a82ad33 |
|---|---|
| 13 $ cvs update -dP | 13 $ cvs update -dP |
| 14 $ ./configure | 14 $ ./configure |
| 15 $ make bootstrap | 15 $ make bootstrap |
| 16 | 16 |
| 17 The bootstrap process makes sure all necessary files are rebuilt | 17 The bootstrap process makes sure all necessary files are rebuilt |
| 18 before it builds the final Emacs binary. | 18 before it builds the final Emacs binary. Unfortunately, it doesn't |
| 19 always work when there are stale files from a previous build in the | |
| 20 directory tree. | |
| 19 | 21 |
| 20 If 'make bootstrap' fails, it may be necessary to do 'make maintainer-clean' | 22 So if 'make bootstrap' fails, it may be necessary first to do 'make |
| 21 followed by configure before trying it again. | 23 maintainer-clean' to clear out these stale files. You can then try |
| 24 again, starting with `./configure'. (Occasionally the loaddefs.el | |
| 25 file gets into a bad state due to changes in the Lisp libraries; this | |
| 26 procedure forces it to be regenerated.) | |
| 22 | 27 |
| 23 Normally, it is not necessary to use "make bootstrap" after every CVS | 28 Normally, it is not necessary to use "make bootstrap" after every CVS |
| 24 update. Unless there are problems, we suggest using the following | 29 update. Unless there are problems, we suggest using the following |
| 25 alternative procedure after you have done "make bootstrap" at least | 30 alternative procedure after you have done "make bootstrap" at least |
| 26 once: | 31 once: |