16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

make<br />

Options<br />

–c dir Attempts to change into the specified directory when make starts up. If<br />

make cannot change to the directory, an error message is printed. This is<br />

useful for recursive makefiles when building in a different directory.<br />

–D macro definition<br />

Define macro on the command line before reading any makefile. Use the<br />

same form as a normal macro definition (macro=string). If you use this<br />

option, make assigns the value to the macro before reading the makefile;<br />

any definition of the same macro contained in the makefile supersedes this<br />

definition.<br />

Note: make uses any macros defined in this way before reading any<br />

makefile, including the startup file. This allows you to define a startup<br />

file by providing a value for MAKESTARTUP on the command line:<br />

make –D MAKESTARTUP=$HOME/project/startup.mk<br />

–E Suppresses reading of the environment. If you do not specify either –E or<br />

–e, make reads the environment before reading the makefile.<br />

–e Reads the environment after reading the makefile. If neither –E nor –e are<br />

specified, make reads the environment before reading the makefile, except<br />

for the SHELL environment variable, which you must explicitly export. This<br />

option does not affect the value of MAKEFLAGS.<br />

–f file Uses file as the source for the makefile description. make ignores the<br />

makefiles specified as prerequisites to the .MAKEFILES target. If you specify<br />

a minus sign (−) in place of file, make reads the standard input. (In other<br />

words, make expects you to enter the makefile from the terminal or to<br />

redirect it from a file.) You can use more than one –f option.<br />

–i Tells make to ignore all errors and continue making other targets. This is<br />

equivalent to the .IGNORE attribute or macro.<br />

–k Makes all independent targets, even if an error occurs. Ordinarily, make<br />

stops after a command returns a nonzero status. Specifying –k tells make<br />

to ignore the error and continue to make other targets, as long as they are<br />

not related to the target that received the error. make does not attempt to<br />

update anything that depends on the target that was being made when the<br />

error occurred.<br />

–n Displays the commands that make would execute to update the chosen<br />

targets, but does not actually execute any recipe lines unless they have a<br />

plus sign (+) command prefix. make displays recipe lines with an at sign<br />

(@) command prefix on standard output (stdout). For more information<br />

about recipe lines, see z/<strong>OS</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> Programming Tools.<br />

392 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference<br />

With group recipes, make displays the commands it uses to update a given<br />

target, but it also executes the commands.<br />

Note: z/<strong>OS</strong> make supports group recipes, but traditional implementations<br />

of make do not. A group recipe signifies a collection of command<br />

lines fed as a unit to the command interpreter. By contrast, make<br />

executes commands in a normal recipe one by one. For more<br />

information about group recipes, see z/<strong>OS</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong><br />

Programming Tools.<br />

If make finds the string $ (MAKE) in a recipe line, it expands it, adds –n to<br />

the MAKEFLAGS, and then executes the recipe line. This enables you to see

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!