unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building cvs emacs on a dual-core machine
Date: Thu, 21 Dec 2006 01:27:32 +0200	[thread overview]
Message-ID: <uodpykv17.fsf@gnu.org> (raw)
In-Reply-To: <emc8fq$e33$1@sea.gmane.org> (message from Eric Lilja on Wed, 20 Dec 2006 22:03:56 +0100)

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Wed, 20 Dec 2006 22:03:56 +0100
> 
> Ok, here's where it errors out (same with --jobs=2 and --jobs=4):
> gcc -I. -DWIN32_LEAN_AND_MEAN -D_WIN32_WINNT=0x0400 -D_X86_=1 -c 
> -mno-cygwin -mtune=pentium4 -O2  -Di386 -D_CRTAPI1
> =_cdecl    -o oo-spd/i386/preprep.o preprep.c
> gcc -o oo-spd/i386/preprep.exe \
>                      -mno-cygwin  oo-spd/i386/preprep.o
> 
> Essential Lisp files seem to be missing.  You should either
> do `make bootstrap' or create `lisp/abbrev.elc' somehow.
> 
> mingw32-make: *** [maybe-bootstrap-SH] Error 255
> 
> Yes, sorry, I'm on Windows.

That's an important piece of knowledge ;-)

What version of Make do you have?  What does "mingw32-make --version"
print?  The --jobs option started to work correctly on Windows only in
the latest version 3.81 of GNU Make.  If you don't have that version
of Make, --jobs will be very unreliable on Windows.

Also, note that, since the jobserver feature in Make is currently not
suppoorted on Windows, the sub-Make's are invoked with the implied
"--jobs=1" option, in effect defeating parallelism in recusrive Make
invocations.  You will have to tweak the recursive Make invocations in
the Makefile's to explicitly pass the --jobs=2 option to recursive
Make's, in order to see parallelism in subdirectories.

Also, what port of sh.exe do you have?

> You mentioned build log, what else information can I provide to help 
> track this problem down?

Instead of just "mingw32-make --jobs=4 bootstrap" run this command
(from the CMD prompt):

   mingw32-make --jobs=4 --debug=j bootstrap 2>&1 | tee build.txt

The file build.txt will then capture all the output of the build
session; post that file here.

(I assume that you have a port of GNU `tee'; if not, you will have to
install it, or capture the session output in some other way.)

I see already a few problems with --jobs related to Windows, but I'd
like to see the information requested above to make sure I don't miss
anything.

TIA

  reply	other threads:[~2006-12-20 23:27 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 [this message]
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
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=uodpykv17.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).