unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Lilja <mindcooler@gmail.com>
Subject: Re: Building cvs emacs on a dual-core machine
Date: Wed, 03 Jan 2007 21:56:00 +0100	[thread overview]
Message-ID: <enh58o$r8q$1@sea.gmane.org> (raw)
In-Reply-To: <uslf6kcel.fsf@gnu.org>

Eli Zaretskii wrote:
>> From: Eric Lilja [snip raw email address quote]
>> Date: Sat, 23 Dec 2006 12:24:21 +0100
>>
>> Another rebuild: Without jobs, ~11 minutes
> 
> Same here.  I get between 11 and 13 minutes, depending on whether I
> use "-j 2" or not.  This is a single-core system with a 3-GHz
> hyper-threaded CPU.
> 
>> With jobs: Will not complete. :-(
> 
> Please show me the error messages which prevented it from finishing.

Sorry for the delay, but I have been gone for most of the holidays. Hope 
you notice my update to this old thread (easy to miss if you use gmane 
like me).

Anyway, I just performed a full checkout and was able to build emacs 
using the following script:

#!/bin/bash
export CVS_RSH="ssh"
touch ~/.cvspass
cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs co emacs
rm ~/.cvspass
cd emacs/nt/
./configure.bat --with-gcc --no-cygwin --no-debug
time mingw32-make bootstrap --jobs=2 XMFLAGS="--jobs=2"
mingw32-make install

Same system as before. So with the changes you made I can now perform a 
full bootstrap when specifying the jobs parameter. :-) I didn't try to 
build without specifying jobs, but I'm sure it works if this script 
works (and it does). Thanks for fixing this! As you mentioned, 
specifying jobs provide no real benefit under windows at the moment but 
it still feels good that this has been fixed.

- Eric

  reply	other threads:[~2007-01-03 20:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 11:47 Building cvs emacs on a dual-core machine Eric Lilja
2006-12-20 14:40 ` Kim F. Storm
2006-12-20 19:05   ` Eli Zaretskii
2006-12-21 11:04     ` Kim F. Storm
2006-12-22 14:39     ` Chris Moore
2006-12-22 21:37       ` Eli Zaretskii
2006-12-22 23:39         ` Chris Moore
2006-12-20 18:54 ` Eli Zaretskii
2006-12-20 19:48   ` Eric Lilja
2006-12-20 21:03     ` Eric Lilja
2006-12-20 23:27       ` Eli Zaretskii
2006-12-21  0:14         ` Eric Lilja
2006-12-22 21:50           ` Eli Zaretskii
2006-12-22 23:30             ` Eric Lilja
2006-12-23  1:50               ` Eli Zaretskii
2006-12-23  2:04                 ` Eric Lilja
2006-12-23 10:42                   ` Eli Zaretskii
2006-12-23 10:59                     ` Eric Lilja
2006-12-23 11:24                       ` Eric Lilja
2006-12-23 12:46                         ` Eli Zaretskii
2007-01-03 20:56                           ` Eric Lilja [this message]
2007-01-04  4:15                             ` Eli Zaretskii
2007-01-04 20:17                             ` Randal L. Schwartz
2007-01-04 21:59                               ` Eli Zaretskii
2006-12-23  1:54             ` Juanma Barranquero
2006-12-23  9:53               ` Eli Zaretskii
2006-12-20 22:19 ` Richard Stallman
2006-12-26 19:22   ` Randal L. Schwartz
2006-12-27 21:16     ` Richard Stallman

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='enh58o$r8q$1@sea.gmane.org' \
    --to=mindcooler@gmail.com \
    /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).