Re: [bug #41246] Allow to switch shell batch mode at runtime instead of build time

[Eli Zaretskii]

> Date: Thu, 6 Feb 2014 06:23:46 +0900
> From: Mike Hommey <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden
> 
> On Wed, Feb 05, 2014 at 11:10:11PM +0200, Eli Zaretskii wrote:
> > > Date: Thu, 6 Feb 2014 05:58:08 +0900
> > > From: Mike Hommey <address@hidden>
> > > Cc: address@hidden, address@hidden, address@hidden
> > > 
> > > But the thing is there is still inconsistency in how things end up being
> > > invoked whether
> > > - make calls them directly
> > > - make uses sh -c
> > > - make uses sh script.sh
> > 
> > When the shell is a Unixy one, only the first 2 methods are used, and
> > they are used exactly like on Posix platforms.
> 
> Except when make is built with BATCH_MODE_SHELL_ONLY.

Indeed, that's what that compile time option is for.  But if that
option messes up Make (does it?), we probably should delete it.

> Which is needed when sh -c fucks up with double quotes.

I asked for test cases where this happens.  Does this happen only when
backslashes are used in file names?  If so, I don't think that
matters, since backslashes aren't supposed to be used in file names
when a Unixy shell is used.