From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
eggert@cs.ucla.edu, alan@idiocy.org, 36332@debbugs.gnu.org
Subject: bug#36332: non-GUI build broken on macOS
Date: Sun, 23 Jun 2019 16:11:21 +0200 [thread overview]
Message-ID: <m2blyoie7q.fsf@gmail.com> (raw)
In-Reply-To: <83wohdm3ix.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Jun 2019 05:36:22 +0300")
>>>>> On Sun, 23 Jun 2019 05:36:22 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Sat, 22 Jun 2019 22:55:10 +0200
>> Cc: Alan Third <alan@idiocy.org>, Paul Eggert <eggert@cs.ucla.edu>,
>> 36332@debbugs.gnu.org
>>
>> Glenn Morris <rgm@gnu.org> writes:
>>
>> > Before least week, "extraclean" wasn't a particularly well-formed target.
>> > Now it apparently needs to be buildable.
>> > So I suggest that it doesn't delete src/macuvs.h.
>>
>> I think that's a good solution.
Eli> I'm OK with not removing it. However, let's also mention this in the
Eli> description of "extraclean" in the top-level Makefile.in, to the
Eli> effect that if someone wants to force regenerating macuvs.h (e.g.,
Eli> because IVD_Sequences.txt was updated), they might need to remove this
Eli> file manually.
master builds again for me on macOS. Apologies for being grumpy
earlier.
Thanks
Robert
next prev parent reply other threads:[~2019-06-23 14:11 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
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 [this message]
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=m2blyoie7q.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=36332@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.