From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@linux-m68k.org>, Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: poll_for_input_1 undefined
Date: Sun, 13 Jul 2014 08:58:41 -0700 [thread overview]
Message-ID: <53C2ACB1.10100@cs.ucla.edu> (raw)
In-Reply-To: <m2sim5zpnb.fsf@linux-m68k.org>
I think Richard's problem this time was caused not by clock skew, but
because 'bzr up' significantly changed the build procedure, and then 'cd
src; make -k' did not propagate those changes properly.
I took a shot at fixing this and installed the fix as trunk bzr 117526.
This fixes only the src subdirectory; I expect lib-src, lisp, and nt
need similar fixes, but one step at a time.
It is a pain that this build-procedure stuff needs to be semi-copied
around from one makefile to another. One possibility to avoid this
pain, if someone has the time, would be to switch Emacs to a
non-recursive 'make' style [1], which we've already done in other GNU
projects (e.g., coreutils) to good effect. Another possibility would be
to use Automake.
[1] Miller P. Recursive make considered harmful. AUUGN 1998
Feb;19(1):14-25. http://aegis.sourceforge.net/auug97.pdf
next prev parent reply other threads:[~2014-07-13 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 16:57 poll_for_input_1 undefined Richard Stallman
2014-07-11 17:34 ` Dmitry Antipov
2014-07-11 18:12 ` Glenn Morris
2014-07-11 18:19 ` Andreas Schwab
2014-07-12 13:07 ` Richard Stallman
2014-07-12 13:25 ` Andreas Schwab
2014-07-12 23:17 ` Richard Stallman
2014-07-13 7:25 ` Andreas Schwab
2014-07-13 15:58 ` Paul Eggert [this message]
2014-07-12 23:17 ` Richard Stallman
2014-07-13 0:05 ` Glenn Morris
2014-07-13 21:54 ` Richard Stallman
2014-07-14 20:25 ` 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
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=53C2ACB1.10100@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--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).