unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>, emacs-devel@gnu.org
Subject: Re: Pure space overflow (Cygwin)
Date: Fri, 19 Oct 2012 22:45:36 -0400	[thread overview]
Message-ID: <50821050.3050000@cornell.edu> (raw)
In-Reply-To: <837gqm22ol.fsf@gnu.org>

On 10/19/2012 6:09 AM, Eli Zaretskii wrote:
>> Date: Fri, 19 Oct 2012 08:51:17 +0200 (CEST)
>> From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>
>>
>>
>> Ken Brown wrote:
>>
>>> I can't speak for Angelo, but I had to increase it by 2250 to make the
>>> warning go away on my Cygwin build. (This is the regular build, not
>>> the Cygw32 build.)
>>
>> I will try only in this week-end... :-(
>
> I bumped the base value by 80000, so it should solve your problem.
> Perhaps Ken should look into tuning SYSTEM_PURESIZE_EXTRA (on
> conf_post.h) for Cygwin, since no other system seems to have this
> problem at this time.

I could certainly do this, although there's no need at the moment after 
your increase.  Or are you suggesting that I revert your change and then 
tune SYSTEM_PURESIZE_EXTRA for Cygwin?

Ken



  parent reply	other threads:[~2012-10-20  2:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19  6:51 Pure space overflow (Cygwin) Angelo Graziosi
2012-10-19 10:09 ` Eli Zaretskii
2012-10-19 15:55   ` Angelo Graziosi
2012-10-19 17:57   ` chad
2012-10-19 18:44     ` Eli Zaretskii
2012-10-20  2:45   ` Ken Brown [this message]
2012-10-20  8:34     ` Eli Zaretskii
2012-10-20 13:40       ` Ken Brown
  -- strict thread matches above, loose matches on Subject: below --
2012-10-17 22:03 Angelo Graziosi
2012-10-17 23:12 ` Ken Brown
2012-10-17 23:21   ` Glenn Morris
2012-10-18  4:37 ` Eli Zaretskii
2012-10-18 22:44   ` Ken Brown

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=50821050.3050000@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=Angelo.Graziosi@roma1.infn.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).