unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Build failure on Windows
Date: Sun, 5 Mar 2017 13:38:18 -0800	[thread overview]
Message-ID: <0fe30db5-2dfa-add0-e797-7c039225a8f1@cs.ucla.edu> (raw)
In-Reply-To: <58BC8313.40604@gmx.at>

martin rudalics wrote:
> I don't know where to go from here.  In the past two weeks I
> bootstrapped more often than in the past five years.  And if I'm not
> mistaken others experienced the same problem.

One possible improvement in this area is to use GNU Make's Automake-like 
features instead of using Automake. This should simplify the gnulib.mk business 
and should cause breakages to be less likely when the build procedure changes. 
We already assume GNU Make, so this should not introduce build dependencies. I 
mentioned this in January when we had similar build problems with macOS, but 
never got around to doing it. I'll try to bump the priority of this. See:

http://lists.gnu.org/archive/html/emacs-devel/2017-01/msg00097.html



  reply	other threads:[~2017-03-05 21:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 10:20 Build failure on Windows martin rudalics
2017-03-05 11:03 ` Andy Moreton
2017-03-05 13:27   ` martin rudalics
2017-03-05 15:23     ` Eli Zaretskii
2017-03-05 17:59       ` martin rudalics
2017-03-05 18:32         ` martin rudalics
2017-03-05 20:03           ` Eli Zaretskii
2017-03-05 21:28             ` martin rudalics
2017-03-06  3:27               ` Eli Zaretskii
2017-03-06  8:10                 ` martin rudalics
2017-03-05 20:02         ` Eli Zaretskii
2017-03-05 21:28           ` martin rudalics
2017-03-05 21:38             ` Paul Eggert [this message]
2017-03-06  3:30               ` Eli Zaretskii
2017-03-06  3:29             ` Eli Zaretskii
2017-03-06  8:11               ` martin rudalics
2017-03-06 16:08                 ` Eli Zaretskii
2017-03-06 17:45                   ` martin rudalics
2017-03-06 18:48                     ` Eli Zaretskii
2017-03-07  9:45                       ` martin rudalics
2017-03-07 15:44                         ` Eli Zaretskii
2017-03-07 16:13                           ` martin rudalics
2017-03-07 16:23                             ` Eli Zaretskii
2017-03-05 15:19   ` Eli Zaretskii
2017-03-05 18:10     ` Andy Moreton
2017-03-05 20:06       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 18:28 Eric Hanchrow

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=0fe30db5-2dfa-add0-e797-7c039225a8f1@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=andrewjmoreton@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).