From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 11:29:35 +0000 [thread overview]
Message-ID: <a2d812f2ba2cc1432435@heytings.org> (raw)
In-Reply-To: <87zgevvfb2.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
>> Isn't the effect of "make extraclean; make" to rebuild Emacs with the
>> default configuration options (contrary to "make bootstrap", which uses
>> "bootstrap-clean", and with which the configuration options are kept)?
>> Am I missing something?
>
> I'm not quite sure what you're asking here, so I may be missing
> something. :-)
😉
>
> After a "make extraclean", there's nothing more to remove, so saying
> "make" or "make bootstrap" are identical in effect. So there's no point
> in advising people to say "make extraclean; make bootstrap".
>
Exactly, so I think neither of use missed something! 😃
My point here is that this advice will be displayed after a failed make
bootstrap, and that just telling to use "make extraclean; make" is not
clear enough, its effect might be surprising (e.g. the toolkit could
change from Lucid to GTK). Given that its effect is to rebuild Emacs with
the default configuration options, the two possible wordings are:
run "make extraclean" and run "make" again, to rebuild Emacs with the
default configuration options, which might fix the problem
or:
run "make bootstrap configure=default", to rebuild Emacs with the default
configuration options, which might fix the problem
Those two commands are equivalent, but I find the latter clearer, and it's
not obscure, it repeats something that can already be found in
INSTALL.REPO.
next prev parent reply other threads:[~2022-09-19 11:29 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
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 [this message]
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=a2d812f2ba2cc1432435@heytings.org \
--to=gregory@heytings.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).