From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Daniel Colascione <dancol@dancol.org>
Cc: 17215@debbugs.gnu.org, David Kastrup <dak@gnu.org>
Subject: bug#17215: Acknowledgement (Build failure)
Date: Sat, 12 Apr 2014 09:19:57 -0400 [thread overview]
Message-ID: <jwvmwfq8z6a.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <53485FFF.3050301@dancol.org> (Daniel Colascione's message of "Fri, 11 Apr 2014 14:34:55 -0700")
>>> Good question. The reason is largely histerical, where it was
>>> convenient to still have a partly usable Emacs. Nowadays, many more
>>> people build their Emacs from trunk without having the technical
>>> knowledge to detect and handle this problem, so it's probably better to
>>> just abort.
>> I fail to see how an Emacs that segfaults during the build can be
>> considered usable to a degree making sense.
I don't know why it segfaults in the current situation, but usually it
works "just fine", modulo never reclaiming memory.
More specifically, such an Emacs should usually have no trouble
compiling a few .el files (tho the memory growth usually prevents such
an Emacs from recompiling all the .el files).
Stefan
next prev parent reply other threads:[~2014-04-12 13:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 8:08 bug#17215: Build failure David Kastrup
2014-04-07 20:47 ` Glenn Morris
2014-04-08 10:42 ` David Kastrup
2014-04-08 10:50 ` Daniel Colascione
2014-04-08 11:36 ` David Kastrup
2014-04-09 10:19 ` Nicolas Richard
2014-04-09 10:48 ` Daniel Colascione
2014-04-09 12:43 ` Stefan Monnier
2014-04-09 15:38 ` Bastien
[not found] ` <handler.17215.B.139685811224063.ack@debbugs.gnu.org>
2014-04-11 15:51 ` bug#17215: Acknowledgement (Build failure) David Kastrup
2014-04-11 19:11 ` Daniel Colascione
2014-04-11 20:10 ` Eli Zaretskii
2014-04-11 20:18 ` Stefan Monnier
2014-04-11 20:11 ` Stefan Monnier
2014-04-11 20:58 ` David Kastrup
2014-04-11 21:34 ` Daniel Colascione
2014-04-12 13:19 ` Stefan Monnier [this message]
2014-04-12 8:35 ` Eli Zaretskii
2014-04-12 13:21 ` Stefan Monnier
2014-04-12 14:18 ` 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=jwvmwfq8z6a.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17215@debbugs.gnu.org \
--cc=dak@gnu.org \
--cc=dancol@dancol.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).