Thank you, both Eli *and* Paul!! I'm getting a better understanding of what is going on now.
item 1: lint-nt.exe is a win32 executable, though I don't think it matters here. item 2: using double-quotes around the arguments with parens, did not work - but using single-quotes *did* work, at least for lintraw argument; thanks!! Although I use unix utilities extensively, I'm *not* very skilled with shell-command syntax... item 3: SHELL=cmd.exe *also* made the lintraw target work, even without the quotes; that's very cool!! In fact, SHELL=cmd.exe makes *both* targets work!! Thank you all for your insights and suggestions!! On Fri, Dec 4, 2015 at 10:58 AM, Eli Zaretskii [via Gnu - Make] < ml-node+s2324884n16746...@n4.nabble.com> wrote: > > Date: Fri, 4 Dec 2015 10:13:11 -0800 (PST) > > From: Gorlash <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=16746&i=0>> > > > > Okay, here are runs using your make.exe, with two different run styles: > > 'make lint' runs with the 'cmd /c' wrapper, 'make lintraw' just runs the > > program itself. Both still fail, as shown below. > > Thanks, but that doesn't help me help you in any way, as I cannot try > this myself, and don't even know what all these parameters mean or why > they have this peculiar form. I don't even know if lint-nt is a > program or a batch file. > > Once again, as long as a Unixy shell is running the commands, you > _must_ use the quoting style of that shell, and you must protect > characters special for the shell by quoting them. > > > BTW, the sh.exe that make is picking up, is in \git\bin; I cannot really > > delete that, since git uses it for other purposes. > > Then say SHELL=cmd.exe at the beginning of the Makefile, and Make will > use cmd.exe instead of sh.exe. > > > What would be desirable would be if make would spawn processes using > > OS methods such as exec(), rather than trying to spawn sub-shells in > > the Unix style... > > Make already does that. But if your command includes characters > special for the shell, it always invokes a sub-shell, because it > doesn't want to implement all the convoluted logic of the shell with > handling those special characters. > > _______________________________________________ > Help-make mailing list > [hidden email] <http:///user/SendEmail.jtp?type=node&node=16746&i=1> > https://lists.gnu.org/mailman/listinfo/help-make > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://gnu-make.2324884.n4.nabble.com/problems-running-certain-utilities-via-makefile-Win32-tp16736p16746.html > To unsubscribe from problems running certain utilities via makefile > (Win32), click here > <http://gnu-make.2324884.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=16736&code=ZG1pbGxlckB2aXRhbGNvbm5lY3QuY29tfDE2NzM2fC01MDg3MTY3NzY=> > . > NAML > <http://gnu-make.2324884.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://gnu-make.2324884.n4.nabble.com/problems-running-certain-utilities-via-makefile-Win32-tp16736p16748.html Sent from the Gnu - Make - Help mailing list archive at Nabble.com. _______________________________________________ Help-make mailing list Help-make@gnu.org https://lists.gnu.org/mailman/listinfo/help-make
