From: Glenn Morris <rgm@gnu.org>
To: Jorgen Schaefer <forcer@forcix.cx>, 17629@debbugs.gnu.org
Subject: bug#17629: Can't build emacs-24 branch
Date: Thu, 29 May 2014 12:06:26 -0400 [thread overview]
Message-ID: <mld2ewy3gd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83sinshbio.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 May 2014 18:04:15 +0300")
Eli Zaretskii wrote:
>> In a fresh checkout and with a clean tree:
>
> This doesn't seem to be a clean tree:
[...]
> Did you switch to the emacs-24 branch in the same git repository, and
> then typed the command above? If so, either "make bootstrap" or clone
> a separate repository, switch to emacs-24 there, and then your
> commands should work.
>
> In Emacs development, the trunk and the release branch diverge very
> quickly, so "make clean" is not enough to give you a "clean tree".
The main point is that `make clean' does not delete the compiled lisp
files (and cannot, since they are prebuilt in lisp tarfiles).
`make maintainer-clean', or `make bootstrap' does.
Always use `make bootstrap' if CPU time is not a factor, even when
building the same branch.
(Presumably this issue is going to occur more in the git-era, since it
doesn't have shared repos.)
next prev parent reply other threads:[~2014-05-29 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 11:07 bug#17629: Can't build emacs-24 branch Jorgen Schaefer
2014-05-29 14:47 ` Paul Eggert
2014-05-29 15:04 ` Eli Zaretskii
2014-05-29 16:06 ` Glenn Morris [this message]
2014-05-29 16:31 ` Jorgen Schaefer
2014-05-29 16:56 ` Glenn Morris
2014-05-29 17:28 ` Stefan Monnier
2014-05-29 19:12 ` Glenn Morris
2014-05-29 20:33 ` Stefan Monnier
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=mld2ewy3gd.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17629@debbugs.gnu.org \
--cc=forcer@forcix.cx \
/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.