[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Two problems on MacOS Catalina...
From: |
Alan Third |
Subject: |
Re: Two problems on MacOS Catalina... |
Date: |
Mon, 18 Nov 2019 20:36:37 +0000 |
User-agent: |
Mutt/1.12.0 (2019-05-25) |
On Mon, Nov 18, 2019 at 11:17:03AM -0500, Perry E. Metzger wrote:
> On Sun, 17 Nov 2019 18:15:31 -0500 "Perry E. Metzger"
> <address@hidden> wrote:
> > On Sun, 17 Nov 2019 19:19:16 +0000 Alan Third <address@hidden>
> > 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.
> Also, I had to explicitly disable harfbuzz or the build gave me an
> error that it had detected but was not using it (whatever that
> meant).
That’s very strange. I have harfbuzz installed using brew and
configure is clever enough to ignore it.
Was this error before or after doing make bootstrap?
--
Alan Third