From: Kenichi Handa <handa@m17n.org>
Subject: dump-emacs doesn't fail even if Pure Lisp storage overflows
Date: Fri, 20 Jan 2006 16:41:48 +0900 [thread overview]
Message-ID: <E1Ezqu4-0001hM-00@etlken> (raw)
I've just increased BASE_PURESIZE to 1190000 because it
seems that Solaris requires more pure bytes than GNU/Linux.
But, the problem is that building of Emacs proceeds even if
this message is shown:
Pure Lisp storage overflow (approx. 1173352 bytes needed)
And, the resulting emacs behaves very strangely.
Shouldn't we stop the building by error in such a case?
---
Kenichi Handa
handa@m17n.org
next reply other threads:[~2006-01-20 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 7:41 Kenichi Handa [this message]
2006-01-20 17:51 ` dump-emacs doesn't fail even if Pure Lisp storage overflows Stefan Monnier
2006-01-24 11:25 ` Kenichi Handa
2006-01-20 22:58 ` Richard M. Stallman
2006-01-22 0:48 ` Juri Linkov
2006-01-22 2:15 ` Luc Teirlinck
2006-01-22 3:19 ` Luc Teirlinck
2006-01-23 1:54 ` Juri Linkov
2006-01-22 17:44 ` Richard M. Stallman
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=E1Ezqu4-0001hM-00@etlken \
--to=handa@m17n.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).