[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU make doesn't use windows cmd.exe shell

From: Sebastian WAGNER
Subject: Re: GNU make doesn't use windows cmd.exe shell
Date: Tue, 24 Aug 2010 17:07:11 +0200

No, when I set the SHELL variable nothing changes.
I don't have the cygwin\bin in my PATH, to see if it works. So when I start the make I get bin\sh: command not found -> this is why I think it is still trying to use the cygwin sh shell.

Not shure if this is a bug...!?

Anyway, I will try to use MinGW .. hope that it works correctly.

On Tue, Aug 24, 2010 at 4:40 PM, Greg Chicares <address@hidden> wrote:
On 2010-08-23 08:20Z, Sebastian WAGNER wrote:
> I have a problem with the latest GNU make version 3.81-2 running on a
> Windows XP system (using cygwin) and hope that you can help me.

3.82 is now available:

> I used a very old make version before and wanted to upgrade. Now it seems
> that make runs in the sh.exe shell and doesn't find the paths for the tools.
> I need to run it on the cmd.exe shell and tried to set a environment
> variable SHELL = c:\windows\system32\cmd.exe as described in the release
> notes. But this doesn't seem to work.

If it says
 make: c:windowssystem32cmd.exe: Command not found
then you might instead try writing forward slashes:
 SHELL = c:/windows/system32/cmd.exe

But, as long as you're using cmd.exe instead of sh, it would probably
be better to use a native 'make'. It should build right out of the box,
or you can download a precompiled binary here:

Mit freundlichen Grüßen

Sebastian Wagner

Valeo Wischersysteme GmbH
Abteilung TEB
Poststräßle 10
74321 Bietigheim-Bissingen

phone:  +49(0)7142 / 73 - 3228
fax:       +49(0)7142 / 73 - 3035
email: address@hidden

Valeo Wischersysteme GmbH
Sitz der Gesellschaft: 74321 Bietigheim-Bissingen
Handelsregister: Amtsgericht Stuttgart - HRB 30 1794
Geschäftsführer: Holger Schwab, Jean-Marc André
Vorsitzender des Aufsichtsrates: Knudt-Alexander Ziems

This e-mail message is intended only for the use of the intended recipient(s).
The information contained therein may be confidential or privileged,
and its disclosure or reproduction is strictly prohibited.
If you are not the intended recipient, please return it immediately to its sender 
at the above address and destroy it. 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]