From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Kangas <stefan@marxist.se>,
Gregory Heytings <gregory@heytings.org>,
emacs-devel@gnu.org, Po Lu <luangruo@yahoo.com>
Subject: Re: master 3fd2b00a4b 2/2: ; * Makefile.in: Add "make bootstrap configure=default" as a first choice.
Date: Mon, 19 Sep 2022 14:33:10 +0200 [thread overview]
Message-ID: <878rmfv915.fsf@gnus.org> (raw)
In-Reply-To: <jwvh713womp.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 19 Sep 2022 08:15:41 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> `make bootstrap` should focus on fixing the bootstrap issues that can be
> present in ELisp files. It's there so as to avoid the need for
> a complete recompile-from-scratch for those of us who don't have
> machines which can recompile the world under 2min.
The difference in time between a "make bootstrap" and a "make
extraclean; make" is about 0.5% in my tests (1m8.1s vs 1m7.7s). (The
absolute time difference will vary, of course, but the percentage
shouldn't, I'd imagine.)
But, sure, the name doesn't really make much difference -- it'd just be
nice to have instructions for users that are as clear and easy as
possible. The current answer -- "make extraclean; make" isn't quite
good enough, especially since that can fail if you've already done, say,
a "bootstrap-clean".
But since we've already advising people to say "make bootstrap", it'd be
less of an adjustment for the few developers that need that extra 0.5%
speed to adjust their typing to "make bootstrap-mostly", in my opinion.
next prev parent reply other threads:[~2022-09-19 12:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166357331345.19427.12446846086384744693@vcs2.savannah.gnu.org>
[not found] ` <20220919074155.2E6D7C00872@vcs2.savannah.gnu.org>
2022-09-19 7:46 ` master 3fd2b00a4b 2/2: ; * Makefile.in: Add "make bootstrap configure=default" as a first choice Po Lu
2022-09-19 7:52 ` Gregory Heytings
2022-09-19 7:50 ` Lars Ingebrigtsen
2022-09-19 7:52 ` Po Lu
2022-09-19 7:53 ` Gregory Heytings
2022-09-19 7:59 ` Lars Ingebrigtsen
2022-09-19 8:01 ` Po Lu
2022-09-19 9:29 ` Gregory Heytings
2022-09-19 9:41 ` Lars Ingebrigtsen
2022-09-19 10:13 ` Stefan Kangas
2022-09-19 12:15 ` Stefan Monnier
2022-09-19 12:25 ` Po Lu
2022-09-19 12:33 ` Lars Ingebrigtsen [this message]
2022-09-19 12:51 ` Po Lu
2022-09-19 13:02 ` Stefan Monnier
2022-09-19 13:04 ` Lars Ingebrigtsen
2022-09-19 13:22 ` Gregory Heytings
2022-09-19 18:41 ` Lars Ingebrigtsen
2022-09-19 13:37 ` Po Lu
2022-09-19 14:02 ` Eli Zaretskii
2022-09-19 14:14 ` Po Lu
2022-09-19 14:20 ` Eli Zaretskii
2022-09-19 14:54 ` Gregory Heytings
2022-09-19 15:51 ` Eli Zaretskii
2022-09-19 16:02 ` Gregory Heytings
2022-09-19 16:14 ` Eli Zaretskii
2022-09-19 16:30 ` Gregory Heytings
2022-09-19 13:37 ` Gerd Möllmann
2022-09-19 13:46 ` Stefan Monnier
2022-09-19 12:33 ` Gregory Heytings
2022-09-19 10:14 ` Gregory Heytings
2022-09-19 10:17 ` Lars Ingebrigtsen
2022-09-19 11:29 ` Gregory Heytings
2022-09-19 12:23 ` Po Lu
2022-09-19 19:51 ` Gregory Heytings
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=878rmfv915.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).