From: Eli Zaretskii <eliz@gnu.org>
Cc: offby1@blarg.net, emacs-devel@gnu.org
Subject: Re: questions on INSTALL.cvs
Date: Fri, 11 Aug 2006 15:54:00 +0300 [thread overview]
Message-ID: <umzabe8lz.fsf@gnu.org> (raw)
In-Reply-To: <44DBF126.6070704@speakeasy.net> (message from ken on Thu, 10 Aug 2006 22:53:26 -0400)
> Date: Thu, 10 Aug 2006 22:53:26 -0400
> From: ken <gebser@speakeasy.net>
> Cc: emacs-devel@gnu.org
>
> Eric Hanchrow wrote:
> > The INSTALL.cvs file gives the following commands (here numbered for
> > clarity and brevity):
> >
> > A.1.$ ./configure
> > A.2.$ make bootstrap
> >
> > ....
> >
> > B.1.$ ./configure
> > B.2.$ make
> > B.3.$ cd lisp
> > B.4.$ make recompile EMACS=../src/emacs
> > B.5.$ cd ..
> > B.6.$ make
> >
> > I'm building emacs (effectively) for the first time. Have run A.1 and
> > A.2. Do I now run B.1 through B.6?
> >
> > Nope
> >
> > Or does A.1 and A.2 replace B.1 and B.2?
> >
> > Yup
> >
>
> Thanks much. Someone should rewrite INSTALL.cvs a little to make this
> clearer.
Could you please clarify what is unclear there. The text of
INSTALL.CVS begins with this:
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":
$ ./configure
$ make bootstrap
The bootstrap process makes sure all necessary files are rebuilt
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:
$ ./configure
$ make
$ cd lisp
$ make recompile EMACS=../src/emacs
$ cd ..
$ make
The paragraph immediately preceding the second procedure clearly says
that it's an alternative: ``Normally, it is not necessary to use "make
bootstrap"...'' How much clearer can one get?
next prev parent reply other threads:[~2006-08-11 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 23:05 questions on INSTALL.cvs ken
2006-08-10 23:27 ` Eric Hanchrow
2006-08-11 2:53 ` ken
2006-08-11 12:54 ` Eli Zaretskii [this message]
2006-08-11 17:53 ` Bill Wohler
2006-08-12 12:04 ` Eli Zaretskii
2006-08-12 17:16 ` Bill Wohler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=umzabe8lz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=offby1@blarg.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.