before it builds the final Emacs binary.
Normally, it is not necessary to use "make bootstrap" after every CVS
-update. Unless there are problems, we suggest the following
-procedure:
+update. Unless there are problems, we suggest using the following
+alternative procedure after you have done "make bootstrap" at least
+once:
$ ./configure
$ make
(If you want to install the Emacs binary, type "make install" instead
of "make" in the last command.)
-Occasionally the file "lisp/loaddefs.el" will need be updated to reflect
-new autoloaded functions. If you see errors about undefined lisp
-functions during compilation, that may be the reason. Another symptom
-may be an error saying that "loaddefs.el" could not be found; this is
-due to a change in the way loaddefs.el was handled in CVS, and should
-only happen once, for users that are updating old CVS trees.
+Occasionally the file "lisp/loaddefs.el" will need be updated to
+reflect new autoloaded functions. If you see errors about undefined
+lisp functions during compilation, that may be the reason. Another
+symptom may be an error saying that "loaddefs.el" could not be found;
+this is due to a change in the way loaddefs.el was handled in CVS, and
+should only happen once, for users that are updating old CVS trees.
To update loaddefs.el, do:
$ cd lisp
$ make autoloads EMACS=../src/emacs
-If either of above procedures fails, try "make bootstrap".
+If either of the above partial procedures fails, try "make bootstrap".
Users of non-Posix systems (MS-Windows etc.) should run the
platform-specific configuration scripts (nt/configure.bat, config.bat,
etc.) before "make bootstrap" or "make"; the rest of the procedure is
-applicable to those systems as well.
+applicable to those systems as well, except that the value of the
+EMACS variable on the Make command line might be different, e.g.,
+../bin/emacs.exe or some such.
Questions, requests, and bug reports about the CVS versions of Emacs
should be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.help
If you execute cvs commands inside Emacs, specifically if you use
pcl-cvs, output from CVS may be lost due to a problem in the
-interface between ssh, cvs, and libc. Corrupted checkins have
-also been rumored to have happened.
+interface between ssh, cvs, and libc. Corrupted checkins are
+also known to have happened.
To fix the problem, save the following script into a file, make it
executable, and set CVS_RSH to the file name of the script: