From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Two strange messages while building Emacs on MS-Windows
Date: Fri, 07 Dec 2012 23:35:33 +0200 [thread overview]
Message-ID: <83mwxpmtp6.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0g0VjUdMDGfS1+BKbXZ5rcCb_p1zL77eTW=r3+ftTdiCA@mail.gmail.com>
> Date: Fri, 7 Dec 2012 21:17:04 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Emacs development discussions <emacs-devel@gnu.org>
>
> I was following Eli's advice for doing incremental builds
> (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12128#20), since
> bootstrapping takes a lot more time.
That advice wasn't meant to be used for producing distributions, only
for your own use.
> But, why the makefiles don't take care all necessary recompilations?
Because we don't have a good way of tracking dependencies between Lisp
files.
> Being forced to do a full bootstrap is too bad.
Why is it too bad for a distribution you do once in a while? Let it
run in a separate directory, and you can meanwhile do something else.
How much time does it take you to bootstrap, btw? And on what
machine?
> Is not there a better solution for this?
No. Which is why admin/make-tarball.txt, the file documenting the
procedure to produce a release tarball, says:
2. Bootstrap to make 100% sure all elc files are up-to-date, and to
make sure that the later tagged version will bootstrap, should it be
necessary to check it out.
next prev parent reply other threads:[~2012-12-07 21:35 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 19:21 Two strange messages while building Emacs on MS-Windows Dani Moncayo
2012-12-07 19:54 ` Glenn Morris
2012-12-07 19:57 ` Glenn Morris
2012-12-07 20:17 ` Dani Moncayo
2012-12-07 21:35 ` Eli Zaretskii [this message]
2012-12-07 22:11 ` Dani Moncayo
2012-12-07 22:35 ` Stefan Monnier
2012-12-08 8:02 ` Eli Zaretskii
2012-12-08 8:43 ` Dani Moncayo
2012-12-08 9:24 ` Eli Zaretskii
2012-12-08 23:06 ` Stefan Monnier
2012-12-09 3:44 ` Eli Zaretskii
2012-12-09 15:50 ` Stefan Monnier
2012-12-09 18:15 ` Óscar Fuentes
2012-12-09 18:52 ` Eli Zaretskii
2012-12-09 19:31 ` Óscar Fuentes
2012-12-09 22:14 ` Eli Zaretskii
2012-12-09 22:44 ` Óscar Fuentes
2012-12-10 6:06 ` Eli Zaretskii
2012-12-10 11:11 ` Óscar Fuentes
2012-12-10 14:37 ` Eli Zaretskii
2012-12-10 15:42 ` Óscar Fuentes
2012-12-10 16:20 ` Eli Zaretskii
2012-12-09 22:00 ` Eli Zaretskii
2012-12-09 23:31 ` Dani Moncayo
2012-12-10 6:13 ` Eli Zaretskii
2012-12-10 20:57 ` Dani Moncayo
2012-12-10 21:08 ` Eli Zaretskii
2012-12-10 21:33 ` Dani Moncayo
2012-12-11 6:49 ` Eli Zaretskii
2012-12-11 7:18 ` Dani Moncayo
2012-12-11 7:51 ` Eli Zaretskii
2012-12-11 20:41 ` Dani Moncayo
2012-12-11 21:00 ` Eli Zaretskii
2012-12-11 20:41 ` Dani Moncayo
2012-12-11 21:05 ` Eli Zaretskii
2012-12-11 21:58 ` Dani Moncayo
2012-12-11 22:55 ` Stefan Monnier
2012-12-12 3:50 ` Eli Zaretskii
2012-12-12 14:26 ` Stefan Monnier
2012-12-12 17:18 ` Eli Zaretskii
2012-12-12 18:42 ` Eli Zaretskii
2012-12-12 3:48 ` Eli Zaretskii
2012-12-12 18:41 ` Eli Zaretskii
2012-12-11 7:57 ` Daniel Colascione
2012-12-11 20:42 ` Dani Moncayo
2012-12-11 20:47 ` Daniel Colascione
2012-12-11 20:58 ` Dani Moncayo
2012-12-11 20:59 ` Daniel Colascione
2012-12-11 21:01 ` Dani Moncayo
2012-12-11 21:02 ` Daniel Colascione
2012-12-10 9:59 ` Eli Zaretskii
2012-12-10 10:37 ` Romain Francoise
2012-12-10 14:42 ` Eli Zaretskii
2012-12-10 15:33 ` Romain Francoise
2012-12-10 16:04 ` Eli Zaretskii
2012-12-10 14:44 ` Eli Zaretskii
2012-12-07 22:57 ` joakim
2012-12-08 8:08 ` Eli Zaretskii
2012-12-08 10:58 ` joakim
2012-12-08 11:35 ` Óscar Fuentes
2012-12-08 12:12 ` Óscar Fuentes
2012-12-08 12:44 ` Eli Zaretskii
2012-12-08 13:24 ` Óscar Fuentes
2012-12-08 13:38 ` Eli Zaretskii
2012-12-09 1:18 ` Óscar Fuentes
2012-12-08 12:33 ` Eli Zaretskii
2012-12-07 21:35 ` Stefan Monnier
2012-12-09 3:20 ` Jason Rumney
2012-12-07 20:17 ` Dani Moncayo
2012-12-07 21:24 ` 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
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=83mwxpmtp6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--cc=emacs-devel@gnu.org \
/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).