From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Two strange messages while building Emacs on MS-Windows Date: Sun, 09 Dec 2012 02:18:41 +0100 Message-ID: <87d2ykxbta.fsf@wanadoo.es> References: <83mwxpmtp6.fsf@gnu.org> <83d2ylm0em.fsf@gnu.org> <87y5h8ydy0.fsf@wanadoo.es> <87pq2kyc7e.fsf@wanadoo.es> <83lid8lnlj.fsf@gnu.org> <87hanwy8vs.fsf@wanadoo.es> <83k3ssll3g.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1355015945 7791 80.91.229.3 (9 Dec 2012 01:19:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 9 Dec 2012 01:19:05 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 09 02:19:19 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ThVY4-0007zn-Mp for ged-emacs-devel@m.gmane.org; Sun, 09 Dec 2012 02:19:16 +0100 Original-Received: from localhost ([::1]:60517 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThVXs-00011H-3p for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2012 20:19:04 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThVXp-00011A-RF for emacs-devel@gnu.org; Sat, 08 Dec 2012 20:19:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ThVXo-0006oL-D9 for emacs-devel@gnu.org; Sat, 08 Dec 2012 20:19:01 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:35742) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThVXo-0006oH-6R for emacs-devel@gnu.org; Sat, 08 Dec 2012 20:19:00 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ThVXx-0007rV-9A for emacs-devel@gnu.org; Sun, 09 Dec 2012 02:19:09 +0100 Original-Received: from 126.red-88-13-105.dynamicip.rima-tde.net ([88.13.105.126]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Dec 2012 02:19:09 +0100 Original-Received: from ofv by 126.red-88-13-105.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Dec 2012 02:19:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 82 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 126.red-88-13-105.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:gsWtnJI+n9m/KXswETPelhNKo2Y= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155389 Archived-At: Eli Zaretskii writes: >> From: Óscar Fuentes >> Date: Sat, 08 Dec 2012 14:24:23 +0100 >> >> So Wine is neglecting cmd.exe. Using one from a Windows XP install >> allows the script to complete. Then, buildobj.h causes a failure because >> it contains too much " and '. Apparently make-buildobj-SH: is used >> instead of make-buildobj-CMD. > > Maybe the Windows makefiles assume something that is false in Wine. > The test for the shell type is in nt/gmake.defs: > > # Determine whether make is using sh or cmd/command as shell; cmd.exe > # will output "ECHO is on" when echo is given by itself, while sh will > # not produce any output. > sh_output := $(shell echo) > ifeq "$(findstring ECHO, $(sh_output))" "ECHO" > THE_SHELL = $(COMSPEC)$(ComSpec) > SHELLTYPE=CMD > SWITCHCHAR=/ > else > USING_SH = 1 > THE_SHELL = $(SHELL) > SHELLTYPE=SH > > Which part(s) of this do(es)n't work in Wine? cmd.exe from Wine outputs Echo is off (note the capitalization), while the one taken from the Spanish Windows XP outputs ECHO está activado I don't know why the test fails with that cmd.exe, it was copied from the virtual machine where I build Emacs. Possibly my mistake, because at some point I realized that COMSPEC was not set and restarted the whole process, but maybe some generated makefile was not deleted. BTW, Wine's cmd.exe seems unable to get the quoting right while generating buildobj.h. I tried multiple combinations, but haven't found a method for outputting one double-quote to the file. >> mingw32-make[1]: Entering directory `D:/exp/emacs/emacs/lib-src' >> mmingw32-make[1]: Leaving directory `D:/exp/emacs/emacs/lib-src' >> ingw32-make[1]: *** No rule to make target `../lisp/abbrev.elc', needed by `DOC'. Stop. >> mingw32-make: *** [all-other-dirs-gmake] Error 2 > > You need to say "make bootstrap" explicitly, the Windows build scripts > cannot automatically intuit that a bootstrap is needed. Yes, I started with `make bootstrap' but, after fixing buildobj.h, just executed `make'. [snip] After undoing the workarounds for the DOC target mentioned on my previous message and commenting out the test for the shell type quoted at the beginning of this one, hence forcing all makefiles to use the copied cmd.exe, the build continued all along, except for about 30 .el files which failed to compile crashing emacs but didn't stop the build. Then `make install' failed with mingw32-make[2]: Entering directory `D:/exp/emacs/emacs/lisp' cp -f *.el "d:\exp\emacs\installed/lisp" fixme:process:CmdBatNotification 1 cp: cannot stat `*.el': Invalid argument fixme:process:CmdBatNotification 0 mingw32-make[2]: *** [install-lisp-CMD] Error 1 mingw32-make[2]: Leaving directory `D:/exp/emacs/emacs/lisp' The `fixme' comes from Wine, there are a lot of them about CmdBatNotification. The second most popular is fixme:msvcrt:MSVCRT__sopen_s : pmode 0x81b6 ignored At this point I gave out, as Wine seems too unreliable for the task. Also I had the impression that the Wine build is slower than the virtualized Windows XP build running on the same physical machine.