Lines Matching refs:shell

18    5. The $(shell) built-in can run arbitrary complex commands,
20       shell.
93    6. After Make finishes, if you have a Unix-style shell installed,
107       Without a Unix-style shell, you will have to install programs
123    7. The `clean' targets also require Unix-style shell, and GNU Sed
127       shell (I used the DJGPP port of Bash 2.03), Perl, Sed, Fileutils
134    1. The shell issue.
141       the shell or internal shell commands, because that is faster.
142       When shell features like redirection or filename wildcards are
143       involved, Make calls the shell.
150       When the $SHELL variable points to a Unix-style shell, Make
151       works just like you'd expect on Unix, calling the shell for any
152       command that involves characters special to the shell or
153       internal shell commands.  The only difference is that, since
156       command line to a temporary disk file and then invokes the shell
159       If $SHELL points to a DOS-style shell, however, Make will not
164       pipes.  Therefore, when presented with a DOS shell, this port of
165       Make will emulate most of the shell functionality, like
166       redirection and pipes, and shall only call the shell when a
167       batch file or a command internal to the shell is invoked.  (Even
168       when a command is an internal shell command, Make will first
175       `system' where it would invoke the shell on Unix.  The most
182       call Unix shell scripts directly, provided that the shell whose
188       The $(shell) built-in is implemented in this port by calling
190       are valid for $(shell) as well.  In particular, you can put
192       inside $(shell), which is in many cases a valid substitute for
203       directive if the basename of the shell name (like `sh' in the
211       defined to the exact pathname of that file, and that shell will
213       shell is *not* found, the line which sets it will be effectively
216       the shell, I feel it doesn't make any sense to tailor Make's
217       behavior to a shell which is nowhere to be found.
222       pathname of the shell, including the filename extension.
229       environment *is* used to set the shell (since on MSDOS, it's
230       unlikely that the interactive shell will not be suitable for
234       of the targets require a real (i.e. Unix-like) shell, which will
235       nevertheless work when such shell is not available (provided, of
237       require such a shell).  More important, you can convert Unix
238       Makefiles to MSDOS and leave the line which sets the shell
239       intact, so that people who do have Unixy shell could use it for
292       you use a Unix-style shell (where a backslash is a quote