On Tue, Apr 14, 2015 at 03:04:28PM -0500, Earl Hood wrote:
> On Tue, Apr 14, 2015 at 2:21 PM, Chris Barlock wrote:
> > Thank you, Steve. If I make the executable="/bin/sh" and uncomment the
> > protoc command, I get:
>
> You need the -c option to /bin/sh to indicate it should execute the command
> that follows on the argument list.
To expand on that a little,
/bin/sh <something>
expects that <something> is a text file with a set of shell commands in
it to be interpreted and executed by sh. This is somewhat simplified
since the first line could tell sh to use some other program to
interpret and execute the rest of the file but for our purposes, the
simplification is OK. If <something> is a binary executable then you
get various interesting error messages that essentially mean it wasn't
what sh was looking for. sh then fails and ant reports the error you
got. By putting -c before <something> you tell /bin/sh that <something>
is an executable file that should be executed directly. That's what you
would want for the original problem but apply is much cleaner.
--
--Steve
"It must not be forgotten that it is especially dangerous
to enslave men in the minor details of life." Alexis de Tocqueville
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
