unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Stefan Monnier <monnier+gnu/emacs@RUM.cs.yale.edu>, emacs-devel@gnu.org
Subject: Re: Emacs-diffs digest, Vol 1 #508 - 12 msgs
Date: Mon, 25 Mar 2002 11:29:04 -0500	[thread overview]
Message-ID: <200203251629.g2PGT4s13115@rum.cs.yale.edu> (raw)
In-Reply-To: 3099-Sat23Mar2002115331+0200-eliz@is.elta.co.il

> What is the reason for this change in src/Makefile.in?  Are you
> saying that the default value of PURESIZE is large enough to load
> *.el files in source form?
> 
>     - /* Build a temacs with a sufficiently large PURESIZE to load the
>     -    Lisp files from loadup.el in source form.  */
>     - 
>     - bootstrap-temacs: 
>     - 	LC_ALL=C $(MAKE) $(MFLAGS) temacs ALL_CFLAGS="$(ALL_CFLAGS) -DPURESIZE=5000000 -I../src"
>     - 

Overflowing the pure area is not a problem.  It's only a performance
issue, which is irrelevant during bootstrap.  Check my patch to
alloc.c committed around the same time.

> Also, is it wise to avoid building DOC during the bootstrap?  Are we
> sure it will never be used?

The DOC file built during bootstrap is not 100% correct and has
to be scrapped and rebuilt once we have the elc files.

I think it'd be a bug if compiling a .el file requires the DOC file.


	Stefan


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-25 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16oZ1I-0001u2-00@fencepost.gnu.org>
2002-03-23  9:53 ` Emacs-diffs digest, Vol 1 #508 - 12 msgs Eli Zaretskii
2002-03-25 16:29   ` Stefan Monnier [this message]
2002-03-25 20:10     ` Eli Zaretskii
2002-03-25 22:40       ` Stefan Monnier
2002-03-26  5:58         ` Eli Zaretskii
2002-03-26 15:31           ` bootstrap (was: Emacs-diffs digest, Vol 1 #508 - 12 msgs) 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

  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=200203251629.g2PGT4s13115@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --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).