From: chad <yandros@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Tim Cross <theophilusx@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
EMACS development team <emacs-devel@gnu.org>
Subject: Re: extraclean and admin/grammars [was Re: Git master head build failure?]
Date: Sat, 3 Apr 2021 15:36:51 -0700 [thread overview]
Message-ID: <CAO2hHWY3ZYah90zF2AZoDyJXOMsAt39opLMHdmQ-nt9reDMQrw@mail.gmail.com> (raw)
In-Reply-To: <83o8eve9oy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
On Sat, Apr 3, 2021 at 7:16 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > I still don't understand what mean here, since it's been demonstrated
> > several times that (in certain circumstances) people have to say "make
> > extraclean" to build a working Emacs executable.
>
> "make extraclean" is only needed when doing something very drastic,
> like switching to a very different branch. That is an extremely rare
> (if not improbable) use case, so IMO having everyone pay for it is
> unjustified.
>
> > So "make bootstrap" doesn't do what it says on the tin
>
> But it does: it bootstraps the current configuration of Emacs by doing
> what is necessary, but not more than that.
>
> It sounds like you think that "make bootstrap" is equivalent to
> checking out a pristine clone. But that is not the case, at least not
> for most people who use that target.
>
Without getting too caught up in the details of who-said-what-when, when I
read the Makefile, this text:
# make bootstrap
> # Removes all the compiled files to force a new bootstrap from a
> # clean slate, and then build in the normal way.
..it makes me think something much closer to what I think Lars was saying
"make bootstrap" should do than "only use this if you don't have
src/{t,}emacs", which is roughly how I interpret (perhaps wrongly) what Eli
is suggesting "make boostrap" is for. It also surprises me that emacs'
build system needs clean, mostlyclean, distclean, maintainer-clean,
extraclean, and bootstrap, but that overhead seems very low, mostly
confusion around which to use.
Probably, I'm biased by my own use-case, which is roughly: I periodically
(multiple times a week) pull and bootstrap emacs using a custom build
script, so I can test the latest and greatest of emacs-devel. When I do
work on specific changes myself, I use "make all" nearly all the time (I
have memories of needing to bootstrap now and then, but I can't recall the
circumstances). That said, I'm using a moderately performant machine,
(currently 3 years old, before that up to 8 years old) and typically run
-j6.
Hope that helps.
~Chad
[-- Attachment #2: Type: text/html, Size: 2829 bytes --]
next prev parent reply other threads:[~2021-04-03 22:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 2:41 Git master head build failure? Tim Cross
2021-04-01 3:04 ` Stefan Monnier
2021-04-01 3:10 ` Tim Cross
2021-04-01 7:33 ` Eli Zaretskii
2021-04-01 8:57 ` Tim Cross
2021-04-01 9:17 ` tomas
2021-04-01 9:56 ` Daniel Brooks
2021-04-01 9:36 ` Gregor Zattler
2021-04-01 10:11 ` Andreas Schwab
2021-04-01 7:25 ` Eli Zaretskii
2021-04-01 8:34 ` Tim Cross
2021-04-01 9:00 ` Eli Zaretskii
2021-04-01 10:56 ` Stefan Kangas
2021-04-01 13:03 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:02 ` Eli Zaretskii
2021-04-01 13:01 ` Eli Zaretskii
2021-04-01 13:03 ` Stefan Monnier
2021-04-01 13:07 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:36 ` Eli Zaretskii
2021-04-01 15:32 ` Stefan Monnier
2021-04-01 15:37 ` Eli Zaretskii
2021-04-01 16:05 ` extraclean and admin/grammars [was Re: Git master head build failure?] Glenn Morris
2021-04-01 16:09 ` Lars Ingebrigtsen
2021-04-01 16:19 ` Lars Ingebrigtsen
2021-04-02 4:19 ` Tim Cross
2021-04-02 5:58 ` Eli Zaretskii
2021-04-02 13:41 ` Lars Ingebrigtsen
2021-04-02 13:58 ` Eli Zaretskii
2021-04-01 18:31 ` Eli Zaretskii
2021-04-02 13:40 ` Lars Ingebrigtsen
2021-04-02 13:57 ` Eli Zaretskii
2021-04-03 13:30 ` Lars Ingebrigtsen
2021-04-03 14:15 ` Eli Zaretskii
2021-04-03 22:36 ` chad [this message]
2021-04-04 7:20 ` Eli Zaretskii
2021-04-03 23:52 ` Tim Cross
2021-04-04 7:39 ` Eli Zaretskii
2021-04-04 19:44 ` Lars Ingebrigtsen
2021-04-01 17:15 ` Stefan Monnier
2021-04-01 19:56 ` Eli Zaretskii
2021-04-01 20:13 ` Stefan Monnier
2021-04-03 7:58 ` Eli Zaretskii
2021-04-13 2:20 ` Stefan Monnier
2021-04-13 11:51 ` Eli Zaretskii
2021-04-13 12:19 ` Eli Zaretskii
2021-04-13 13:01 ` Stefan Monnier
2021-04-13 12:59 ` Stefan Monnier
2021-04-13 14:03 ` Eli Zaretskii
2021-04-01 18:29 ` Eli Zaretskii
2021-04-04 16:28 ` Glenn Morris
2021-04-04 17:12 ` Eli Zaretskii
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=CAO2hHWY3ZYah90zF2AZoDyJXOMsAt39opLMHdmQ-nt9reDMQrw@mail.gmail.com \
--to=yandros@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
--cc=theophilusx@gmail.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).