all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Daniel Colascione <dancol@dancol.org>,
	 Emacs developers <emacs-devel@gnu.org>
Subject: Re: About 'eager' warnings
Date: Sat, 26 Apr 2014 01:05:10 +0200	[thread overview]
Message-ID: <535AEA26.3000802@alice.it> (raw)
In-Reply-To: <535AE2CC.2090905@dancol.org>



Il 26/04/2014 00:33, Daniel Colascione ha scritto:
> On 04/25/2014 03:29 PM, Angelo Graziosi wrote:
>> Il 24/04/2014 02:30, Daniel Colascione ha scritto:
>>>
>>> Thanks for the report. The (harmless) issue is present in emacs-24 too,
>>> so I installed a fix there as r117014.
>>>
>>
>> Sometimes, in the build log, I find the message:
>>
>> [...]
>> Compiling gnus/gnus-int.el
>> Eager macro-expansion failure: (error "Memory exhausted--use C-x s then
>> exit and restart Emacs")
>> Wrote /work/emacs/lisp/gnus/gnus-html.elc
>> Compiling gnus/gnus-kill.el
>> [...]
>>
>> and sometimes, repeating the build (same trunk), it goes away.
>>
>> What does the message mean? That happens on Win7 64 for the cygw32 build
>> (on Cygwin64). The machine is an Athlon 64 Dual Core with 4 GiB of  RAM.
>> Usually the build is done with Chrome, Thunderbird, Emacs, Cygwin
>> console (mintty) running.
>>
>> Sound strange that "Memory exhausted"...
>
> That's weird. If you keep repeating the build, can you repro it? What

No. Sometimes the build succeeds without "failure" messages


Ciao,
Angelo.




  reply	other threads:[~2014-04-25 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 23:26 About 'eager' warnings Angelo Graziosi
2014-04-24  0:30 ` Daniel Colascione
2014-04-25 22:29   ` Angelo Graziosi
2014-04-25 22:33     ` Daniel Colascione
2014-04-25 23:05       ` Angelo Graziosi [this message]
2014-04-24  0:33 ` Stefan Monnier

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=535AEA26.3000802@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=dancol@dancol.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 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.