|> I've just had a look at the GNU make info page (File: make.info, Node:
|> Execution) and they say at this page that make executes all commands
|> useing a subshell and that it uses /bin/sh as subshell if the $(SHELL)
|> variable is not set.
|>
|> So it invokes a subshell anyway (regardless if $(SHELL) is set or not).
No, it doesn't. If SHELL is unset or set to /bin/sh then make will parse
the command by itself, unless it is complex (containing shell
metacharacters) or uses shell builtin commands or if $IFS is non-standard.
See job.c:construct_command_argv_internal. From the user's point of view
this does not make any difference (except performance-wise), that's why
it's not documented except in the sources.
-- Andreas Schwab "And now for something schwab@issan.informatik.uni-dortmund.de completely different" schwab@gnu.org- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html