Re: sh.exe needed to bootstrap on Windows?

[Juanma Barranquero]

On 7/17/07, Eli Zaretskii <address@hidden> wrote:

> Thanks.  But I think it's good that I made the change in the Windows
> bootstrap procedure anyway, because there's always a chance that some
> other command or hook that runs during bootstrap will need a shell.

This change is perhaps not needed anymore:

2004-06-06  Juanma Barranquero  <address@hidden>

       * makefile.w32-in (bootstrap-nmake): When nmake'ing bootstrap on
       the lisp/ directory, set SHELL to $(SHELLTYPE); this avoids
       calling non-existent cmdproxy.exe on boostrappings after a
       previous install followed by realclean.

The problem was that a successful bootstrap/install created the
SHELL=cmdproxy.exe registry entry, so subsequent bootstraps failed
because cmdproxy.exe wasn't there.

The change was:

Index: nt/makefile.w32-in
===================================================================
RCS file: /cvsroot/emacs/emacs/nt/makefile.w32-in,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -2 -r1.22 -r1.23
--- nt/makefile.w32-in  3 May 2004 13:51:23 -0000       1.22
+++ nt/makefile.w32-in  6 Jun 2004 01:59:43 -0000       1.23
@@ -140,5 +140,5 @@
       $(MAKE) $(MFLAGS) bootstrap-clean
       cd ..\lisp
-       $(MAKE) $(MFLAGS) bootstrap
+       $(MAKE) $(MFLAGS) SHELL=$(SHELLTYPE) bootstrap
       cd ..\lib-src
       $(MAKE) $(MFLAGS) DOC

            Juanma