From: Paul Eggert <eggert@cs.ucla.edu>
To: Angelo Graziosi <angelo.graziosi@alice.it>, Eli Zaretskii <eliz@gnu.org>
Cc: rcopley@gmail.com, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Last commit breaks macOS build
Date: Fri, 6 Jan 2017 15:43:16 -0800 [thread overview]
Message-ID: <8cc0ec3d-81b0-df0a-f6a7-9e59d69c8190@cs.ucla.edu> (raw)
In-Reply-To: <72df92d3-af60-1005-fc5e-e039619e1f91@alice.it>
On 01/06/2017 03:33 PM, Angelo Graziosi wrote:
>
> Now, if I understand, 'nt' should refer to the build on MSW: Why,
> then, the same message in the build on GNU/Linux and on macOS?
Becuase nt/gnulib.mk is built by the developer with special tools like
'autoconf', not by the builder who merely starts with a tarball and runs
'configure; make' and should not need the special tools.
The whole thing is a bit of a mess, and the mess is largely caused by
Emacs using Automake, and Automake is needed only because of Gnulib
(because Gnulib assumes Automake for portability to older systems
lacking GNU Make). I'll look into fixing this so that Gnulib no longer
assumes Automake, so that Emacs can stop relying on Automake. Since
Emacs assumes GNU Make, it doesn't need Automake (except for the Gnulib
code, which I think I can fix).
next prev parent reply other threads:[~2017-01-06 23:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 10:08 Last commit breaks macOS build Angelo Graziosi
2017-01-05 3:21 ` Paul Eggert
2017-01-05 9:30 ` Richard Copley
2017-01-05 9:54 ` Angelo Graziosi
2017-01-05 15:42 ` Eli Zaretskii
2017-01-05 16:16 ` Eli Zaretskii
2017-01-05 16:37 ` Angelo Graziosi
2017-01-05 17:04 ` Eli Zaretskii
2017-01-05 17:21 ` Angelo Graziosi
2017-01-05 17:52 ` Eli Zaretskii
2017-01-05 18:18 ` Andreas Schwab
2017-01-05 18:24 ` Eli Zaretskii
2017-01-05 18:32 ` Andreas Schwab
2017-01-05 18:38 ` Eli Zaretskii
2017-01-05 18:53 ` Andreas Schwab
2017-01-05 19:38 ` Eli Zaretskii
2017-01-05 22:41 ` Angelo Graziosi
2017-01-06 7:45 ` Eli Zaretskii
2017-01-06 23:33 ` Angelo Graziosi
2017-01-06 23:43 ` Paul Eggert [this message]
2017-01-05 16:24 ` 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=8cc0ec3d-81b0-df0a-f6a7-9e59d69c8190@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rcopley@gmail.com \
--cc=schwab@linux-m68k.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).