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: Sat, 23 Dec 2006 11:59:20 +0100	[thread overview]
Message-ID: <emj266$4k2$1@sea.gmane.org> (raw)
In-Reply-To: <uvek2ki69.fsf@gnu.org>

Eli Zaretskii skrev:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Sat, 23 Dec 2006 03:04:30 +0100
>>
>> I cannot build emacs anymore.
> 
> Sorry to hear that, but I cannot reproduce any of the failures on my
> machine, it still bootstraps and builds for me, both with and without
> "--jobs".
> 
>> I didn't specify jobs at all. I tried both cmd.com and cygwin's
>> bash. cmd.com yields:
>> C:\cvsemacs\emacs\nt>mingw32-make bootstrap
>> mkdir "oo-spd"
>> mkdir "oo-spd/i386"
>> echo oo-spd/i386 > stamp_BLD
>> 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/addsection.o addsection.c
>> process_begin: CreateProcess(NULL, 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/addsection.o addsection.c, ...) failed.
>> make (e=2): The system cannot find the file specified.
>               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> I feel terribly stupid, because I cannot figure out what is the file
> it doesn't find here.  It cannot be the oo-spd/i386 directory since it
> was just created before the compilation command.  And it cannot be
> addsection.c, because you are in the nt/ subdirectory, where
> addsection.c lives.  Could you please try to find out what file is
> missing?
> 
>>  From bash:
>> $ mingw32-make bootstrap
>> [...]
>> mingw32-make[1]: Leaving directory `c:/cvsemacs/emacs/lib-src'
>> c:/mingw32-make-3.81-1/bin/mingw32-make   XMFLAGS="" -C ../src bootstrap
>> [Please ignore a syntax error on the next line - it is intentional]
>> /usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
>> /usr/bin/sh: -c: line 1: syntax error: unexpected end of file
>> mingw32-make[1]: Entering directory `c:/cvsemacs/emacs/src'
>> c:/mingw32-make-3.81-1/bin/mingw32-make -w \ temacs CFLAGS='-I. 
>                                              ^^^^^^^^
>> -DWIN32_LEAN_AND_MEAN -D_WIN32_WINNT=0x0400 -D_X86_=
>> 1 -c  -mno-cygwin -mtune=pentium4 -O2  -Di386 -D_CRTAPI1=_cdecl 
>> -Demacs=1 -DWINDOWSNT -DDOS_NT -DHAVE_CONFIG_H -I.
>> ./nt/inc -D_UCHAR_T -DHAVE_NTGUI=1 -DUSE_CRT_DLL=1 -DPURESIZE=5000000'
>> [Please ignore a syntax error on the next line - it is intentional]
>> /usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
>> /usr/bin/sh: -c: line 1: syntax error: unexpected end of file
>> mingw32-make[2]: Entering directory `c:/cvsemacs/emacs/src'
>> mingw32-make[2]: *** No rule to make target ` temacs'.  Stop.
>                                                ^^^^^^^^
> I think I can understand this one; sounds like some bug in the MinGW
> make and/or in its interaction with the Cygwin Bash.  Note the lone
> backslash above and the leading blank in ` temacs'.
> 
> I made some changes to work around this; please resync and try again.
> (Needless to say, it still bootstraps for me, at least without --jobs.
> Will try with --jobs shortly.)

I just performed a fresh checkout and managed to complete the entire 
build bootstrap process without problem (this one without specifying 
--jobs=2). The only thing different from last night was that I had 
upgraded TCI (an alternative to rxvt) to the latest beta but that 
shouldn't make a difference I think. I did this checkout before I saw 
the message I'm replying to now, don't know if I got the changes or not 
but it worked now. I will do a rebuild again and time it this time and 
then time another rebuild this time with --jobs=2 and see if both can 
complete successfully (and their respective times will be interesting 
for me to compare).

- Eric

  reply	other threads:[~2006-12-23 10:59 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 [this message]
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='emj266$4k2$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).