> Date: Thu, 6 Feb 2014 06:23:46 +0900 > From: Mike Hommey <m...@glandium.org> > Cc: psm...@gnu.org, bug-make@gnu.org, bo...@kolpackov.net > > 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 <m...@glandium.org> > > > Cc: psm...@gnu.org, bug-make@gnu.org, bo...@kolpackov.net > > > > > > 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. _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
