From: "Perry E. Metzger" <perry@piermont.com>
To: Alan Third <alan@idiocy.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Two problems on MacOS Catalina...
Date: Mon, 18 Nov 2019 18:01:17 -0500 [thread overview]
Message-ID: <20191118180117.56b2de9d@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <20191118203637.GA84843@breton.holly.idiocy.org>
On Mon, 18 Nov 2019 20:36:37 +0000 Alan Third <alan@idiocy.org> wrote:
> > > > My first thought is to try "make bootstrap;make install" and
> > > > then copy the Emacs.app directory again.
> > >
> > > I will try that and report back.
> >
> > That works. But: it was never necessary to "make bootstrap"
> > before to get a working emacs. What has changed, and can it be
> > documented in INSTALL?
>
> Sometimes it is necessary. I don’t know why but some changes to the
> codebase have required ‘make bootstrap’ for as long as I’ve been
> building Emacs. Usually a number of people post to emacs-dev asking
> why they can’t build master any more.
In that case, I think it would be good to document this in INSTALL.
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2019-11-18 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 22:40 Two problems on MacOS Catalina Perry E. Metzger
2019-11-17 19:19 ` Alan Third
2019-11-17 23:15 ` Perry E. Metzger
2019-11-18 16:17 ` Perry E. Metzger
2019-11-18 20:36 ` Alan Third
2019-11-18 23:00 ` Perry E. Metzger
2019-11-19 7:51 ` Lars Ingebrigtsen
2019-11-18 23:01 ` Perry E. Metzger [this message]
2019-11-19 3:37 ` Eli Zaretskii
2019-11-18 16:54 ` Filipp Gunbin
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=20191118180117.56b2de9d@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=alan@idiocy.org \
--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).