all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Third <alan@idiocy.org>
Cc: 36332@debbugs.gnu.org
Subject: bug#36332: non-GUI build broken on macOS
Date: Sat, 22 Jun 2019 13:25:58 -0700	[thread overview]
Message-ID: <48becc24-d7f6-bf9a-dea0-d2cf893b7142@cs.ucla.edu> (raw)
In-Reply-To: <20190622201943.GD57900@breton.holly.idiocy.org>

Alan Third wrote:

> I haven’t been following the clean build chat on emacs-devel, does
> make extraclean delete macuvs.h?

Yes, and this was true even before the recent patches in this area.
> We could try returning a useful message at configure time instead of
> just failing during the build. Do you think the attached patch is OK?

Sure, that looks good.

> I’d rather not just build headless as the usual build process on the
> Mac is to do ’make; make install’

My idea is that plain 'make' would build a headless Emacs for src/temacs and 
src/bootstrap-emacs, as that's all that Emacs needs to compile itself. However, 
src/emacs would continue to be an Emacs with the GUI. This could be done on all 
platforms, not just macOS. Admittedly it'd be some work.





  reply	other threads:[~2019-06-22 20:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-22 18:46 bug#36332: non-GUI build broken on macOS Paul Eggert
2019-06-22 19:38 ` Alan Third
2019-06-22 19:44   ` Paul Eggert
2019-06-22 20:19     ` Alan Third
2019-06-22 20:25       ` Paul Eggert [this message]
2019-06-22 20:37         ` Alan Third
2019-06-22 20:50       ` Glenn Morris
2019-06-22 20:55         ` Lars Ingebrigtsen
2019-06-22 21:10           ` Alan Third
2019-06-23  2:36           ` Eli Zaretskii
2019-06-23 14:11             ` Robert Pluim
2019-06-25  1:43             ` Glenn Morris
2019-06-25 11:24               ` Lars Ingebrigtsen
2019-06-27  9:45                 ` Paul Eggert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48becc24-d7f6-bf9a-dea0-d2cf893b7142@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=36332@debbugs.gnu.org \
    --cc=alan@idiocy.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.