From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, stefan@marxist.se,
gregory@heytings.org, emacs-devel@gnu.org
Subject: Re: master 3fd2b00a4b 2/2: ; * Makefile.in: Add "make bootstrap configure=default" as a first choice.
Date: Mon, 19 Sep 2022 17:02:23 +0300 [thread overview]
Message-ID: <83tu53xy1c.fsf@gnu.org> (raw)
In-Reply-To: <87wn9zmqo2.fsf@yahoo.com> (message from Po Lu on Mon, 19 Sep 2022 21:37:01 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Stefan Kangas
> <stefan@marxist.se>, Gregory Heytings <gregory@heytings.org>,
> emacs-devel@gnu.org
> Date: Mon, 19 Sep 2022 21:37:01 +0800
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > But why use the name "bootstrap" for something like that? "Bootstrap"
> > implies that it's built from the ground up.
>
> I always thought the "bootstrap" implied building the Lisp part of Emacs
> from the ground up.
No, "bootstrap" means just that: build a program when some components
needed for the build are missing. Thus, "bootstrap" is not
necessarily supposed to make sense when those components are present.
We are actually using "bootstrap" in a different role: as a build from
a clean tree. (And when you actually build a fresh checkout, it is
nowadays unnecessary to say "make bootstrap", as GNUmakefile does TRT
in that case if you just say "make".)
So maybe we should repurpose "bootstrap", and rename it while at that,
to something like "clean-build" or somesuch.
next prev parent reply other threads:[~2022-09-19 14:02 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
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 [this message]
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=83tu53xy1c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.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).