all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: BASE_PURESIZE
Date: Sat, 05 Aug 2006 18:23:42 +0200	[thread overview]
Message-ID: <v91wrv40dt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <uirl7ldsp.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Aug 2006 12:41:58 +0300")

On Sat, Aug 05 2006, Eli Zaretskii wrote:

>> From: Nick Roberts <nickrob@snap.net.nz>
>> Date: Sat, 5 Aug 2006 14:16:54 +1200
>> 
>> I get the warning message "Building Emacs overflowed pure space".
>> Assuming this is related to decreasing BASE_PURESIZE, the argument
>> for keeping it to a minimum for computers with little memory
>> against the inconvenience of repeatedly tripping over it, is
>> completely lost on me.
>
> No, it was decreased because we made a change lately that lowers the
> required pure size by several tens of KB, IIRC.

FWIW, starting with this change, I had to set SITELOAD_PURESIZE_EXTRA
also[1] on the machine (SUSE 10.0 [2]) on which it wasn't necessary
until some weeks before this change.

Unless we find (and fix) the reason for the different pure space
requirements, it would be good to increase BASE_PURESIZE to an amount
that allows building Emacs without an overflow on most machines, I
think.

Bye, Reiner.

[1] I still need to increase it on the machines as reported
    previously[3].  On i686 (2x Intel Xeon (2.40GHz)) and x86_64 (AMD
    Athlon 64 3500+):

$ gcc --version
gcc (GCC) 3.3.4 (pre 3.3.5 20040809)
[...]
$ cat /etc/SuSE-release 
SuSE Linux 9.2 (i586)         [... or x86_64 resp.]
VERSION = 9.2

[2] i686 (Intel(R) Pentium(R) M processor 1500MHz):
$ cat /etc/SuSE-release 
SUSE LINUX 10.0 (i586) OSS
VERSION = 10.0
$ gcc --version
gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux)

[3] See the thread around
    <http://thread.gmane.org/v9d5diibsr.fsf%40marauder.physik.uni-ulm.de>.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2006-08-05 16:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  2:16 BASE_PURESIZE Nick Roberts
2006-08-05  9:41 ` BASE_PURESIZE Eli Zaretskii
2006-08-05 16:23   ` Reiner Steib [this message]
2006-08-05 18:51     ` BASE_PURESIZE Richard Stallman
2006-08-05 20:07       ` BASE_PURESIZE Reiner Steib
2006-08-06  4:43         ` BASE_PURESIZE Richard Stallman
2006-08-06  9:19           ` BASE_PURESIZE Reiner Steib
2006-08-06 19:40         ` BASE_PURESIZE Reiner Steib
     [not found]           ` <jebqqx393g.fsf@sykes.suse.de>
2006-08-07  3:53             ` BASE_PURESIZE Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2009-10-23 11:00 BASE_PURESIZE Eli Zaretskii
2009-10-23 11:39 ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:10   ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:24     ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:35       ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:50         ` BASE_PURESIZE Andreas Schwab
2009-10-24 10:05     ` BASE_PURESIZE Eli Zaretskii
2009-10-24 10:37       ` BASE_PURESIZE Andreas Schwab
2009-10-24 13:18         ` BASE_PURESIZE Eli Zaretskii
2009-10-24 17:27           ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 19:01             ` BASE_PURESIZE Stefan Monnier
2009-10-25  8:24               ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 19:04             ` BASE_PURESIZE Chong Yidong
2009-10-24 19:16               ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 11:58 ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 14:24 ` BASE_PURESIZE Juanma Barranquero
2009-10-24  4:41   ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24  6:47     ` BASE_PURESIZE Dan Nicolaescu
2009-10-24  8:24       ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24 10:22     ` BASE_PURESIZE Eli Zaretskii
2009-10-24 11:14       ` BASE_PURESIZE Stephen J. Turnbull

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=v91wrv40dt.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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.