Eli Zaretskii wrote: >> From: Eric Lilja >> 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. $ mingw32-make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i686-pc-mingw32 > > 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? $ sh.exe --version GNU bash, version 3.2.9(10)-release (i686-pc-cygwin) Copyright (C) 2005 Free Software Foundation, Inc. > >> 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. I ran it and I'm attaching build.txt, but I ran it from TCI running bash instead of a regular cmd prompt, hope that I still was able to provide you with the information you needed. > > TIA - Eric