unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Confusion in INSTALL.CVS instructions
@ 2008-10-09 18:22 Harry Putnam
  2008-10-10  2:24 ` Eric Hanchrow
  0 siblings, 1 reply; 4+ messages in thread
From: Harry Putnam @ 2008-10-09 18:22 UTC (permalink / raw)
  To: emacs-devel

Developers:

I found the `INSTALL.CVS' file that accompanies a cvs check out of
emacs sources to be confusing on what the progression of commands is
supposed to be.

Here is the section that I find confusing:

>          Building and Installing Emacs from CVS

> Some of the files that are included in the Emacs tarball, such as
> byte-compiled Lisp files, are not stored in the CVS repository.
> Therefore, to build from CVS you must run "make bootstrap" instead
> of just "make":

>   $ cvs update -dP
>   $ make bootstrap

> Of course, if this is the first time you go through it, you'll need
> to do ./configure before the "make bootstrap".

> Normally, it is not necessary to use "make bootstrap" after every
> CVS update.  "make" should work in 90% of the cases and be much
> quicker.

>   $ make

> (If you want to install the Emacs binary, type "make install"
> instead of "make" in the last command.)

It's not clear if on a fresh checkout one is supposed to run both 
`make bootstrap'  and `make'  or  if  `make bootstrap'  takes  the 
place  of `make'.

It may not have confused anyone else but I suspect it does.

I'm currently waiting for make bootstrap to finish.  





^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-10-19  3:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-09 18:22 Confusion in INSTALL.CVS instructions Harry Putnam
2008-10-10  2:24 ` Eric Hanchrow
2008-10-19  2:34   ` Jay Belanger
2008-10-19  3:06     ` Stefan Monnier

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).