unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Sieger <sean.sieger@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Failed to compile from last bzr repo
Date: Mon, 04 Apr 2011 20:13:07 -0400	[thread overview]
Message-ID: <8739lxeess.fsf@gmail.com> (raw)
In-Reply-To: jwvpqp1zo0q.fsf-monnier+emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

    >> Unfortunately, bootstrap on Windows takes a very long time
    > In my setup it takes ~20 min. It is much longer in yours, or do you
    > consider 20 min a very long time?

    On one of my setups it takes about 4mins (8 dual core AMD chips help),
    but that's not one I can use as easily as my fit-pc2 desktop where it
    takes just a tiny bit loner (especially with -O0 and all assertions
    enabled).  It takes long enough there that I don't even know how long
    because I usually only do it when I can swap to some other long task.

:)  I've never timed the bootstrap; intuitively, I come back to the
build, check to see that it runs with a few idiosyncratic functions and
move on with make info and so on.  I just figure the possible waste of
time, let alone other's time and additionally building again (given not
bootstrapping in the first place) doesn't work for me.  I don't recall
my Unix build process (and rarely bootstrapping a second time after an
initial one) taking much less time ... I think I'm just always pleased
with the reward of a wonderful GNU Emacs (and come on, folks, I know
some of you jaded son-of-guns still experience some wonderment).  I'm in
NYC, I can get a pint of ice cream or a quart of milk in 5 minutes round
trip, building Emacs in what ever time it happens to be is Worth It.




  parent reply	other threads:[~2011-04-05  0:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  9:46 Failed to compile from last bzr repo Bastien
2011-04-04 11:53 ` Eli Zaretskii
2011-04-04 12:22   ` Deniz Dogan
2011-04-04 12:38     ` Sean Sieger
2011-04-04 17:37       ` Eli Zaretskii
2011-04-04 21:19         ` Juanma Barranquero
2011-04-04 21:51           ` Stefan Monnier
2011-04-04 22:00             ` Juanma Barranquero
2011-04-05 13:14               ` Stefan Monnier
2011-04-05 15:39                 ` Sean Sieger
2011-04-05 16:36                   ` Juanma Barranquero
2011-04-05 16:52                     ` Eli Zaretskii
2011-04-05 22:45                       ` Juanma Barranquero
2011-04-06  3:01                         ` Eli Zaretskii
2011-04-06  3:22                           ` Juanma Barranquero
2011-04-06 12:57                             ` Andy Moreton
2011-04-06 13:32                               ` Eli Zaretskii
2011-04-06 14:18                                 ` Juanma Barranquero
2011-04-06 15:47                                   ` Eli Zaretskii
2011-04-06 16:08                                     ` Eli Zaretskii
2011-04-06 16:18                                     ` Juanma Barranquero
2011-04-05 15:41                 ` Sean Sieger
2011-04-05 20:57                   ` Stefan Monnier
2011-04-05  0:13             ` Sean Sieger [this message]
2011-04-05  2:59           ` Eli Zaretskii
2011-04-04 16:39     ` Stefan Monnier
2011-04-04 17:35     ` Eli Zaretskii
2011-04-04 16:26   ` Bastien

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=8739lxeess.fsf@gmail.com \
    --to=sean.sieger@gmail.com \
    --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).