unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Daniel Pfeiffer <occitan@esperanto.org>
Subject: Re: build: Maximum buffer size exceeded
Date: Sun, 9 Feb 2003 13:46:18 +0100	[thread overview]
Message-ID: <20030209134618.61175700.occitan@esperanto.org> (raw)
In-Reply-To: mailman.1670.1044707119.21513.help-gnu-emacs@gnu.org

"Eli Zaretskii" <eliz@is.elta.co.il> skribis:
> > From: Daniel Pfeiffer <occitan@esperanto.org>
> > When I think back I've never built Emacs with gcc 3.2 and no longer have
> > 2.95.  I'm trying to build CVS (and meanwhile also 21.2) with gcc 3.2, glibc
> > 2.2.5, Linux Kernel 2.4.19 (SuSE 8.1):
> > ...
> > Loading international/mule-conf.el (source)...
> > Loading format (source)...
> > Loading bindings (source)...
> > Loading files (source)...
> > Maximum buffer size exceeded
> > make[1]: *** [bootstrap-emacs] Fehler 255

> First, please note that reporting failures to build here is not
> recommended: you should either report them on bug-gnu-emacs@gnu.org

Doesn't seem to be working currently.  I recently got two mails back with:
host mx10.gnu.org [199.232.76.166]: 550 Invalid address in message header

> (for released versions of Emacs), or to emacs-pretest-bug@gnu.org (for
> CVS and pretest versions).  Many Emacs developers don't read this
> forum, so they will never see your report.

Also no answer from them yet, so I tried here in the newsgroup.

> What Emacs is trying to tell you is that when it tried to load
> file.el, it found that file to be more than 128MB, the maximum size of
> a buffer Emacs can handle.  What you need to figure out is how come
> files.el, which is only about 170KB, causes Emacs to think it's much
> larger.

I put an strace into the Makefile, and see that it normally opens a file,
writes Loading... and then reads.  But on the last one, it successfully
opens the file, closes it, yet writes Loading... and then  then goes and
opens and closes it again.

I write "the last one", because each time when I byte-compile it, I get one
file further.  But this is no good, because 21.1, which I'm using to byte
compile gives some error messages.

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

-- GPL 3: take the wind out of Palladium's sails! --
 ------
  -- My other stuff here too, sawfish, make.pl...: --
   ------
    -- http://dapfy.bei.t-online.de/ --

  parent reply	other threads:[~2003-02-09 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 10:39 build: Maximum buffer size exceeded Daniel Pfeiffer
2003-02-08 12:22 ` Eli Zaretskii
     [not found] ` <mailman.1670.1044707119.21513.help-gnu-emacs@gnu.org>
2003-02-09 12:46   ` Daniel Pfeiffer [this message]
2003-02-09 15:56     ` Eli Zaretskii
     [not found]     ` <mailman.1701.1044806415.21513.help-gnu-emacs@gnu.org>
2003-02-09 23:42       ` Daniel Pfeiffer
2003-02-10  5:47         ` 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=20030209134618.61175700.occitan@esperanto.org \
    --to=occitan@esperanto.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.
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).