From: dptd dptd <dptdescribe@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: jpff <jpff@codemist.co.uk>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: How to build master
Date: Wed, 26 Apr 2017 20:18:48 +0200 [thread overview]
Message-ID: <6354F5D3-2272-4685-9047-862045C6E04F@gmail.com> (raw)
In-Reply-To: <CAFyQvY175V2SuC6JfSquVaHYZHM0mQ25v4GQiYgBG25NqP_nMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
> On 24 Apr 2017, at 21:13, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
> On Sun, Apr 23, 2017 at 8:38 AM dptd dptd <dptdescribe@gmail.com <mailto:dptdescribe@gmail.com>> wrote:
> Kaushal - can you explain what is the difference and why “make" doesn’t work but "make bootstrap" does?
>
> See what "make bootstrap" does over here: http://git.savannah.gnu.org/cgit/emacs.git/tree/Makefile.in <http://git.savannah.gnu.org/cgit/emacs.git/tree/Makefile.in>
>
> # make bootstrap
> # Removes all the compiled files to force a new bootstrap from a
> # clean slate, and then build in the normal way.
>
> So bootstrap ensures that you don't try to use old compiled files which might be incompatible with the new source files. I am not a core dev, just a user. But I have noticed that that tends to happen once every few months on so on the master branch.
> --
> Kaushal Modi
>
Thanks for the reply! :)
[-- Attachment #2: Type: text/html, Size: 1916 bytes --]
prev parent reply other threads:[~2017-04-26 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 10:54 How to build master jpff
2017-04-17 11:20 ` Kaushal Modi
2017-04-17 12:46 ` jpff
2017-04-23 12:38 ` dptd dptd
2017-04-24 19:13 ` Kaushal Modi
2017-04-26 18:18 ` dptd dptd [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6354F5D3-2272-4685-9047-862045C6E04F@gmail.com \
--to=dptdescribe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jpff@codemist.co.uk \
--cc=kaushal.modi@gmail.com \
/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 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).