Do not use SHELL_PATH from build system in prepare_shell_cmd on Windows
authorJohannes Sixt <j6t@kdbg.org>
Tue, 17 Apr 2012 07:03:21 +0000 (09:03 +0200)
committerJunio C Hamano <gitster@pobox.com>
Tue, 17 Apr 2012 15:51:54 +0000 (08:51 -0700)
The recent change to use SHELL_PATH instead of "sh" to spawn shell commands
is not suited for Windows:

- The default setting, "/bin/sh", does not work when git has to run the
shell because it is a POSIX style path, but not a proper Windows style
path.

- If it worked, it would hard-code a position in the files system where
the shell is expected, making git (more precisely, the POSIX toolset that
is needed alongside git) non-relocatable. But we cannot sacrifice
relocatability on Windows.

- Apart from that, even though the Makefile leaves SHELL_PATH set to
"/bin/sh" for the Windows builds, the build system passes a mangled path
to the compiler, and something like "D:/Src/msysgit/bin/sh" is used,
which is doubly bad because it points to where /bin/sh resolves to on
the system where git was built.

- Finally, the system's CreateProcess() function that is used under
mingw.c's hood does not work with forward slashes and cannot find the
shell.

Undo the earlier change on Windows.

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
run-command.c
index 2af3e0fa520bcd87d241ed7a3601b14232ad94d5..e4edede8b9f95a0960a170d2cc7bda385778186c 100644 (file)
@@ -94,7 +94,11 @@ static const char **prepare_shell_cmd(const char **argv)
                die("BUG: shell command is empty");
 
        if (strcspn(argv[0], "|&;<>()$`\\\"' \t\n*?[#~=%") != strlen(argv[0])) {
+#ifndef WIN32
                nargv[nargc++] = SHELL_PATH;
+#else
+               nargv[nargc++] = "sh";
+#endif
                nargv[nargc++] = "-c";
 
                if (argc < 2)