> Date: Fri, 18 Aug 2006 10:59:22 -0400
> From: Christopher Faylor <[EMAIL PROTECTED]>
> Cc:
>
> Personally, I think that a "mingw make" should just rely on cmd and a
> "msys make" should rely on sh.
I don't think this is practical: too many people are using GNU Make
with Unix-originated Makefil
On Fri, Aug 18, 2006 at 09:07:33AM -0400, Earnie Boyd wrote:
>Quoting Bill Hoffman <[EMAIL PROTECTED]>:
>
>>At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>>
>>
>>>I don't understand why MinGW's make should be using anything like /bin/sh.
>>>Shouldn't it be using cmd.exe or command.com?
>>>
>>It
Quoting Bill Hoffman <[EMAIL PROTECTED]>:
At 04:48 PM 8/17/2006, Christopher Faylor wrote:
I don't understand why MinGW's make should be using anything like /bin/sh.
Shouldn't it be using cmd.exe or command.com?
cgf
It seems that if it finds sh.exe in the path it uses it.
Remember the chars
On Fri, Aug 18, 2006 at 12:21:41AM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 17:02:30 -0400
>> From: Bill Hoffman
>>
>> At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>>
>> >I don't understand why MinGW's make should be using anything like /bin/sh.
>> >Shouldn't it be using cmd.exe
At 05:10 PM 8/17/2006, Eli Zaretskii wrote:
>I use a shell that is a native Windows program, not a Cygwin
>program. (There could be some quoting conflict between the Cygwin
>and non-Cygwin binaries.)
To reproduce the problem you have to run from a cygwin shell or a msys shell.
-Bill
__
> Date: Thu, 17 Aug 2006 17:02:30 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>
> >I don't understand why MinGW's make should be using anything like /bin/sh.
> >Shouldn't it be using cmd.exe or command.com?
> >
> It seems that if it finds sh
> Date: Thu, 17 Aug 2006 16:31:21 -0400
> From: "William A. Hoffman" <[EMAIL PROTECTED]>
>
> From the cygwin shell the error is:
> c:/cygwin/bin/gcc.exe "a.c" "b.c"
> gcc: a.c b.c: No such file or directory
> gcc: no input files
> c:\hoffman\My Builds\CMakeDev\Tests\COnly\b\make.exe: *** [allgcc
> Date: Thu, 17 Aug 2006 16:22:20 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> #broken
> all:
> c:/Program\ Files/Microsoft\ Visual\ Studio\ .NET\ 2003/Vc7/bin/cl.exe
> "a.c" "b.c"
>
> #CreateProcess(C:\cygwin\bin\sh.exe,C:/cygwin/bin/sh.exe -c "c:/Program\
> Files/Microsoft\ Visua
At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>I don't understand why MinGW's make should be using anything like /bin/sh.
>Shouldn't it be using cmd.exe or command.com?
>
>cgf
It seems that if it finds sh.exe in the path it uses it.
Remember the chars_sh and chars_dos thing that is switched a
On Thu, Aug 17, 2006 at 04:22:20PM -0400, Bill Hoffman wrote:
>As requested by Eli, I am posting the problems I am having with mingw-make
>from a cygwin command line.
>
>
>I narrowed down the major problem with mingw make and my makefiles.
>Looks like a process launching issue. If the files are do
At 04:22 PM 8/17/2006, Bill Hoffman wrote:
>As requested by Eli, I am posting the problems I am having with mingw-make
>from a cygwin command line.
>
>
>I narrowed down the major problem with mingw make and my makefiles.
>Looks like a process launching issue. If the files are double quoted
>and pa
As requested by Eli, I am posting the problems I am having with mingw-make
from a cygwin command line.
I narrowed down the major problem with mingw make and my makefiles.
Looks like a process launching issue. If the files are double quoted
and passed to a full path command it passes both files a
12 matches
Mail list logo
