Re: [Dev-C++] CreateProcess balks during compile operation

[Doug M. <dou...@al...>]

I guess I posted the problem below to the wrong list. I see mostly 
general C++/Windows sw devel questions happening here.  Can somehone 
suggest a place to post an under the hood dev-C++ problem?

Thanks,
Doug

> Running Windows XP SP1, Dev-C++ full install 4.9.8.0.  Created a new 
> console application project and inserted a "hello, world" print 
> statement into the source.  I'm getting some kind of subcommand 
> dispatching error when I try to build:
> 
> ---- process_begin C:\Proj\playpen\process_begin 
> CreateProcess(C:\DJGPP\bin\sh.exe, C:/DJGPP/bin/sh.exe -c "g++.exe -c
>  main.cpp -o main.o -I\"C:/Dev-Cpp/include/c++\" 
> -I\"C:/Dev-Cpp/include/c++/mingw32\" 
> -I\"C:/Dev-Cpp/include/c++/backward\"  -I\"C:/Dev-Cpp/include\"  ", 
> ...) failed. ----- make (e=87) C:\Proj\playpen\make (e=87) The 
> parameter is incorrect. ----- C:\Proj\playpen\Makefile.win [Build 
> Error]  [main.o] Error 87 -----
> 
> I replicated this by going into the source dir with a command prompt 
> and typing "make -f Makefile.win".  Behaves in just the same way.
> 
> It looks to me as though the g++ command isn't getting off the 
> ground. Now, it's odd to me that my Dev-C++ directory try contains no
>  sh.exe at all - you'll note that it's trying to run one from a DJGPP
>  directory that occurs later in the PATH chain.  Which, by the way, 
> is:
> 
> Path=C:\Dev-Cpp\bin;C:\DJGPP\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
>  Files\Common Files\Adaptec Shared\System
> 
> Any clues?  Do I need to update or reinstall to get that sh.exe?
> 
> Thanks in advance Doug
> 
> A follow-up on this problem.
> 
> I can build successfully if I open a Command Prompt window, cd to the
> project dir, and type "make -f Makefile.win -n" to get the commands
> make would issue to build the app, then issue them manually.  This
> works fine, and I get an app that works.
> 
> If I then type, in the Command Prompt window, "Make -f Makfile.win",
> I get the message that nothing needs to be built - again, correctly.
> 
> Assuming that "make -f Makefile.win" is the command issued by the
> Dev-C++ "Execute-->Compile" menu item, this seems to imply that the
> problem lies in the glue between Make and its subcommands, e.g., g++.
> 
> 
> ==> Anybody know what is going on here?  I am working with my second
> install of Dev-C++.  I first was trying to use an executable-only
> version in conjunction with DJGPP.  Could I be dealing with leftover
> cruft from that?
> 
> Doug