all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: bootstrap compiles C files twice
Date: Thu, 05 Jun 2008 06:12:21 +0300	[thread overview]
Message-ID: <uskvsbmne.fsf@gnu.org> (raw)
In-Reply-To: <kttzg9vwg0.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: jasonr@gnu.org,  emacs-devel@gnu.org
> Date: Wed, 04 Jun 2008 15:20:31 -0400
> 
> Eli Zaretskii wrote:
> 
> > No, I meant that perhaps Makefile.in was doing for six years two
> > compilations for a good reason.
> 
> I'm sorry, I can't understand this.

Sorry for being unclear.  I meant to say that there might be a good
reason for compiling the sources twice, and that understanding how and
why did we get rid of the -DPURESIZE= switch on the first of these two
compilations might help us understand that good reason, or realize
that there isn't one.





  reply	other threads:[~2008-06-05  3:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  3:20 bootstrap compiles C files twice Glenn Morris
2008-06-03  5:26 ` Stefan Monnier
2008-06-03 16:14   ` Dan Nicolaescu
2008-06-03  7:55 ` Jason Rumney
2008-06-03 18:26   ` Eli Zaretskii
2008-06-03 18:40     ` Glenn Morris
2008-06-03 19:16       ` Glenn Morris
2008-06-03 20:23       ` Eli Zaretskii
2008-06-03 20:52         ` Dan Nicolaescu
2008-06-04  3:06           ` Eli Zaretskii
2008-06-04  3:14             ` Dan Nicolaescu
2008-06-04  3:57             ` Stefan Monnier
2008-06-04 18:50               ` Eli Zaretskii
2008-06-03 22:18         ` Glenn Morris
2008-06-04  3:15           ` Eli Zaretskii
2008-06-04 19:20             ` Glenn Morris
2008-06-05  3:12               ` Eli Zaretskii [this message]
2008-06-05 19:29                 ` Glenn Morris
2008-06-06  9:39                   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uskvsbmne.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=rgm@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.