From: Eric Lilja <mindcooler@gmail.com>
Subject: Re: Building cvs emacs on a dual-core machine
Date: Wed, 20 Dec 2006 22:03:56 +0100 [thread overview]
Message-ID: <emc8fq$e33$1@sea.gmane.org> (raw)
In-Reply-To: <emc41t$f3o$1@sea.gmane.org>
Eric Lilja skrev:
> Eli Zaretskii skrev:
>>> From: Eric Lilja <mindcooler@gmail.com>
>>> Date: Wed, 20 Dec 2006 12:47:13 +0100
>>>
>>> I recently upgraded my computer with a dual-core CPU. I've been
>>> enjoying nice decreases in compile time in my own projects by
>>> specifying --jobs=2 when invoking make.
>>>
>>> However, when I tried that with emacs it started compiling, very fast
>>> with both cores busy, but the build craps out (sorry, no log) after a
>>> little while.
>>
>> Any such failures are bugs in the Emacs Makefiles, so please be sure
>> to report them with full details, including the build log.
>
> I will. This was with the cvs sources I downloaded yesterday (december
> 19th). I have been trying a few times since the beginning of november
> (that's when I got the dual core cpu), neither have been able to build
> when specifying --jobs=2. I will do a fresh checkout later today and
> hopefully provided you with the details you need.
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. This is from a fresh cvs checkout performed
just now. My previous steps were:
./configure.bat --with-gcc --no-cygwin --no-debug
mingw32-make --jobs=4 bootstrap
You mentioned build log, what else information can I provide to help
track this problem down?
>
>>
>> If you didn't try this with the CVS version or with the latest
>> pretest, please do try one of these, because many problems present in
>> Emacs 21.x are already resolved in the latest development code.
>>
>> Thanks in advance.
>>
>>> Maybe because it tries to build something that depends on something
>>> else that has not been quite finished yet because when multiple jobs
>>> are specified things doesn't happen in serial anymore?
>>
>> A bug-free Makefile should never cause any such trouble, since all the
>> dependencies are supposed to be spelled out in it, and Make will never
>> start building a file until all its prerequisites are built.
>
> - Eric
- Eric
next prev parent reply other threads:[~2006-12-20 21:03 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='emc8fq$e33$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 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.