Re: mingw make problem

2006-08-23 Thread William A. Hoffman
At 11:34 AM 8/23/2006, Eli Zaretskii wrote: >> Date: Tue, 22 Aug 2006 08:08:12 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> >> So, I guess you can say running mingw make from a cygwin shell is not >> supported. > >I don't think the issue is with the shell from which you run Make, I

Re: mingw make problem

2006-08-23 Thread Eli Zaretskii
> Date: Tue, 22 Aug 2006 08:08:12 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > > So, I guess you can say running mingw make from a cygwin shell is not > supported. I don't think the issue is with the shell from which you run Make, I think the issue is which sh.exe is being invoked by

Re: mingw make problem

2006-08-22 Thread Earnie Boyd
Quoting Chris Sutcliffe <[EMAIL PROTECTED]>: > >For the MSYS specific stuff, I think directing it to the the MSYS list >would be an idea. Yes. So, is the mingw32-make not working with sh.exe from MSYS, MSYS specific? Or should that not work, or should that be on the mingw list? I'd take

Re: mingw make problem

2006-08-22 Thread Chris Sutcliffe
Accidentally took this off the list (darn Gmail) On 8/22/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: At 09:10 AM 8/22/2006, Chris Sutcliffe wrote: >>But if you can not run mingw make from an msys shell then what is the point of >>looking for sh.exe in the PATH and setting it to be the

Re: mingw make problem

2006-08-22 Thread William A. Hoffman
At 12:39 AM 8/22/2006, Eli Zaretskii wrote: >> Seems like the old make used to create a .sh file to run the commands. > >That's what I suspected. I don't think we want to go back to the >batch mode, since it's slower. > >So the solution still is to debug what happens on the Cygwin Bash >side. I

Re: mingw make problem

2006-08-21 Thread Eli Zaretskii
> Date: Mon, 21 Aug 2006 22:22:47 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > > make 3.79.1 > c:/Hoffman/testmake/runit.exe "a.c" "b.c" > CreateProcess(C:\cygwin\bin\sh.exe,C:/cygwin/bin/sh.exe > c:\DOCUME~1\hoffman\LOCA > LS~1\Temp\make28162.sh,...) > > make 3.81 > CreateProcess(C:

Re: mingw make problem

2006-08-21 Thread William A. Hoffman
At 10:03 PM 8/21/2006, William A. Hoffman wrote: >At 05:28 AM 8/21/2006, Eli Zaretskii wrote: > >OK, I tried that and it does not work. > >// native make build with HAVE_CYGWIN_SHELL >$ ../make-3.81/WinRel/make >c:/Hoffman/testmake/runit.exe "a.c" "b.c" >command line = {c:\Hoffman\testmake\runit.e

Re: mingw make problem

2006-08-21 Thread William A. Hoffman
At 05:28 AM 8/21/2006, Eli Zaretskii wrote: >I think we've already established that CreateProcess has nothing to do >with the problem. I think the problem is that Bash (which receives >the command line passed by CreateProcess) somehow removes the quotes >from the command line before it passes it

Re: mingw make problem

2006-08-21 Thread Eli Zaretskii
> Date: Sat, 19 Aug 2006 10:30:25 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > It does work with quotes even though it does not need them. Maybe > that is the trick with CreateProcess, you have to find the command > and make sure it is in double quotes. I thi

Re: mingw make problem

2006-08-19 Thread William A. Hoffman
At 02:15 AM 8/19/2006, Eli Zaretskii wrote: >> Date: Fri, 18 Aug 2006 16:53:38 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> Cc: make-w32@gnu.org >> >> runit: >> "c:/hoffman/My Builds/CMakeDev/Tests/COnly/b/run.exe" "a.c" "b.c" >> runit2: >> c:/hoffman/My\ Builds/CMake

Re: mingw make problem

2006-08-19 Thread William A. Hoffman
At 10:21 AM 8/19/2006, Earnie Boyd wrote: >Quoting "William A. Hoffman" <[EMAIL PROTECTED]>: > >> >>I get a different failure when the shell is from msys: >> >> >>c:/cygwin/bin/gcc.exe "a.c" "b.c" >>CreateProcess(C:\msys\1.0\bin\sh.exe,C:/msys/1.0/bin/sh.exe -c >>"c:/cygwin/bin/gcc.exe \"a.c\" \

Re: mingw make problem

2006-08-19 Thread Earnie Boyd
Quoting "William A. Hoffman" <[EMAIL PROTECTED]>: I get a different failure when the shell is from msys: c:/cygwin/bin/gcc.exe "a.c" "b.c" CreateProcess(C:\msys\1.0\bin\sh.exe,C:/msys/1.0/bin/sh.exe -c "c:/cygwin/bin/gcc.exe \"a.c\" \"b.c\"",...) Putting child 0x00a73ca0 (broken) PID 4015

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 16:53:38 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > runit: > "c:/hoffman/My Builds/CMakeDev/Tests/COnly/b/run.exe" "a.c" "b.c" > runit2: > c:/hoffman/My\ Builds/CMakeDev/Tests/COnly/b/run.exe "a.c" "b.c" > > So, if th

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 04:32 PM 8/18/2006, Eli Zaretskii wrote: >> Date: Fri, 18 Aug 2006 15:50:03 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> Cc: make-w32@gnu.org >> >> >all: >> >d:/full/path/to/rundump.exe "a.c" "b.c" >> > >> >d:/full/path/to/rundump.exe "a.c" "b.c" >> >command line = {d:\f

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 15:50:03 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > >all: > >d:/full/path/to/rundump.exe "a.c" "b.c" > > > >d:/full/path/to/rundump.exe "a.c" "b.c" > >command line = {d:\full\path\to\rundump.exe a.c b.c} > >argv[0] = {d:\ful

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 03:02 PM 8/18/2006, Eli Zaretskii wrote: >I tried this program, and it verified that there's no problem on my >system, where sh.exe is a native Windows shell. Here's what I get >with this Makefile rule: > >all: >d:/full/path/to/rundump.exe "a.c" "b.c" > >d:/full/path/to/rundump.exe "

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 14:00:55 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > >If you run this program from that makefile you will see that the command > >line actually received by the program is > > > > c:\full\path\to\runDump.exe "a.c b.c" > > > >Note that

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 02:42 PM 8/18/2006, Eli Zaretskii wrote: >> Date: Fri, 18 Aug 2006 12:56:56 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> Cc: make-w32@gnu.org >> >> >Please note that it is considered a shell character on _all_ systems >> >when a Unixy shell is invoked. I believe the reason is tha

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 12:56:56 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > >Please note that it is considered a shell character on _all_ systems > >when a Unixy shell is invoked. I believe the reason is that a Posix > >shell removes the quotes from the com

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 12:56 PM 8/18/2006, William A. Hoffman wrote: >OK, but there seems to be some extra work that needs to be done in >CreateProcess to get the arguments correct. Brad King who did the process execution stuff in cmake, had similar problems with CreateProcess. I asked him to comment on the issue.

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 12:42 PM 8/18/2006, Eli Zaretskii wrote: >> Date: Fri, 18 Aug 2006 08:58:00 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> Cc: make-w32@gnu.org >> >> Just noticed: >> >> static char sh_chars_sh[] = "#;\"*?[]&|<>(){}$`^"; >> >> Note the \" This is in the #ifdef __MSDOS__ section

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 08:58:00 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > Just noticed: > > static char sh_chars_sh[] = "#;\"*?[]&|<>(){}$`^"; > > Note the \" This is in the #ifdef __MSDOS__ section which I assume > is on for mingw. No, MinGW picks u

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 09:27 AM 8/18/2006, Earnie Boyd wrote: >Only for the "native" binary. It isn't a "bad habit" it is a necessary one. Well changing command line options into full paths is an unfortunate side effect at best. -Bill ___ Make-w32 mailing list Make

Re: mingw make problem

2006-08-18 Thread Earnie Boyd
Quoting "William A. Hoffman" <[EMAIL PROTECTED]>: But I want it to use sh.exe. The makefiles are mostly POSIX, the only non-POSIX thing in them is the driver letter stuff. C:/foo/bar.C. So cmd.exe does not like paths like that. Also, Actually the newer versions of cmd.exe doesn't complai

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Fri, 18 Aug 2006 08:40:55 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > Cc: make-w32@gnu.org > > Strange, If you look at the debug output I sent there is no shell redirection > going on, but sh is being used. Redirection is only one of the reasons. Quotes and shell wildcards a

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
Just noticed: static char sh_chars_sh[] = "#;\"*?[]&|<>(){}$`^"; Note the \" This is in the #ifdef __MSDOS__ section which I assume is on for mingw. Why is " considered a shell character? -Bill ___ Make-w32 mailing list Make-w32@gnu.org http://

Re: mingw make problem

2006-08-18 Thread William A. Hoffman
At 07:07 AM 8/18/2006, Eli Zaretskii wrote: >> Date: Thu, 17 Aug 2006 21:37:37 -0400 >> From: "William A. Hoffman" <[EMAIL PROTECTED]> >> >> >>Make 3.81 adds a feature whereby you can say "SHELL = cmd.exe" and >> >>have it use CMD even if sh.exe is on your PATH. Previous versions of >> >>Make did

Re: mingw make problem

2006-08-18 Thread Eli Zaretskii
> Date: Thu, 17 Aug 2006 21:37:37 -0400 > From: "William A. Hoffman" <[EMAIL PROTECTED]> > > >>Make 3.81 adds a feature whereby you can say "SHELL = cmd.exe" and > >>have it use CMD even if sh.exe is on your PATH. Previous versions of > >>Make didn't allow even that. > > > >This behavior was cont

Re: mingw make problem

2006-08-17 Thread William A. Hoffman
At 05:38 PM 8/17/2006, Christopher Faylor wrote: >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 a