> Date: Thu, 3 Dec 2015 15:12:36 -0800 (PST)
> From: Gorlash
>
> I have been using makefiles for many years, but have historically had
> problems running certain win32 executables via it, though the same command
> works fine in a batch file. One of my more common problem applications is
> lint-n
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.
BTW, the sh.exe that make is picking up, is in \git\bin; I cannot really
delete that, since git uses it
On Fri, 2015-12-04 at 10:13 -0800, Gorlash wrote:
> 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.
FWIW, the way I have dealt with this in the past is to put the \git\cmd
directory on Windows PATH, NOT \git\bin. The \g
Hi Paul!
Yes, I do use other utilities in \git\bin, though only a couple...
I tried experimenting with .ONESHELL, but it didn't solve this problem,
possibly because I don't really understand how to use it properly...
On Fri, Dec 4, 2015 at 10:29 AM, Paul Smith-20 [via Gnu - Make] <
ml-node+s23248
Hi Gorlash,
On the subject of your "syntax error near unexpected token `('" errors,
have you tried putting your parentheses arguments in quotes?
Instead of this:
lint: $(SOURCE_FILES)
$(LINT_TOOL) +v -width(160,4) +fcp -ic:\lint9 mingw.lnt -os(_lint.tmp)
$(SOURCE_FILES)
Try this:
lint:
> Date: Fri, 4 Dec 2015 10:13:11 -0800 (PST)
> From: Gorlash
>
> 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
> From: Paul Smith
> Date: Fri, 04 Dec 2015 13:45:26 -0500
> Cc: Help-make@gnu.org
>
> On Fri, 2015-12-04 at 10:13 -0800, Gorlash wrote:
> > 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.
>
> FWIW, the way I have de
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
