From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Klaus.Zeitler@alcatel-lucent.com, 16717@debbugs.gnu.org
Subject: bug#16717: Dumping: Can't update subspace record
Date: Fri, 14 Feb 2014 00:31:58 -0800 [thread overview]
Message-ID: <52FDD47E.7080404@cs.ucla.edu> (raw)
In-Reply-To: <4bd2iqpz0g.fsf@fencepost.gnu.org>
Glenn Morris wrote:
> Because I totally agree [with requiring GNU make]
I'd also prefer requiring GNU make after the freeze is over. GCC has
required this since GCC 3.4 (April 2004), and it seems to perk along
quite nicely. GCC requires GNU make 3.80 (October 2002) or later; these
days I think it'd be OK for Emacs to bump that to GNU make 3.81 (April
2006) or later.
> I think it would be better to first figure out exactly what HP make did
> not like in the original version.
Trying to nail down exactly what an old proprietary 'make' dislikes is
often more trouble than it's worth. I've had experiences with them not
liking command lines of exactly 1023 bytes, that sort of thing.
> Fails when the installation directory contains spaces.
Sorry about that; fixed in trunk bzr 16717. There are other reasons
installation fails when the destination directory name contains spaces,
at least for me; I'll try to look into that.
next prev parent reply other threads:[~2014-02-14 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 12:26 Dumping: Can't update subspace record Klaus Zeitler
2014-02-10 18:40 ` bug#16717: " Paul Eggert
2014-02-13 14:39 ` Klaus Zeitler
2014-02-13 19:43 ` Paul Eggert
2014-02-13 19:54 ` Glenn Morris
2014-02-13 19:56 ` Glenn Morris
2014-02-13 20:32 ` Eli Zaretskii
2014-02-14 8:31 ` Paul Eggert [this message]
2014-02-14 1:45 ` Stefan Monnier
2014-02-10 18:33 ` Paul Eggert
2014-02-14 7:51 ` Glenn Morris
2014-02-14 17:31 ` Stefan Monnier
2014-02-14 14:42 ` Klaus Zeitler
2014-02-14 15:49 ` 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=52FDD47E.7080404@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=16717@debbugs.gnu.org \
--cc=Klaus.Zeitler@alcatel-lucent.com \
--cc=rgm@gnu.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.