(make_float, Fcons): Clear the markbit at init time.
(make_float, Fcons, Fmake_symbol, allocate_misc): Move the increment
of block_index outside of the macro call.
(Fgarbage_collect): Remove null code.
Building and Installing Emacs from CVSSome of the files that are included in the Emacs tarball, such asbyte-compiled Lisp files, are not stored in the CVS repository.Therefore, to build from CVS you must run "make bootstrap"instead of just "make": $ ./configure $ make bootstrapThe bootstrap process makes sure all necessary files are rebuiltbefore it builds the final Emacs binary.Normally, it is not necessary to use "make bootstrap" after every CVSupdate. Unless there are problems, we suggest the followingprocedure: $ ./configure $ make $ cd lisp $ make recompile EMACS=../src/emacs $ cd .. $ make(If you want to install the Emacs binary, type "make install" insteadof "make" in the last command.)Occasionally the file "lisp/loaddefs.el" will need be updated to reflectnew autoloaded functions. If you see errors about undefined lispfunctions during compilation, that may be the reason. Another symptommay be an error saying that "loaddefs.el" could not be found; this isdue to a change in the way loaddefs.el was handled in CVS, and shouldonly happen once, for users that are updating old CVS trees.To update loaddefs.el, do: $ cd lisp $ make autoloads EMACS=../src/emacsIf either of above procedures fails, try "make bootstrap".Users of non-Posix systems (MS-Windows etc.) should run theplatform-specific configuration scripts (nt/configure.bat, config.bat,etc.) before "make bootstrap" or "make"; the rest of the procedure isapplicable to those systems as well.Questions, requests, and bug reports about the CVS versions of Emacsshould be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.helpor gnu.emacs.bug. Ideally, use M-x report-emacs-bug RET which willsend it to the proper place.