Lines Matching refs:always

396 your commands: you can almost always emulate what such a tool would do
1138 you assign to this variable will be ignored; it will always return
1208 commands but no prerequisites, that file will always be remade (*note
1231 is not always necessary.
1364 A rule is always expanded the same way, regardless of the form:
1370 immediately, and the commands used to construct the target are always
1436 always take place within the scope of the automatic variables for that
1504 rule with the command script is always evaluated last.
2083 always used whether or not the target needs to be built. Thus, if the
2272 the subdirectory obviously always exists; otherwise it won't be built)
2346 depending on this one will always have their commands run.
2509 stamps are always low resolution. You need not list archive
2803 rule, its commands are always executed (even if the target already
2840 must always be very careful to update the makefile every time you add
2870 prerequisites, because it always regenerates any makefile that is out
2943 are always interpreted by `/bin/sh' unless the makefile specifies
3238 `COMSPEC' (which is always set) is used instead.
3319 standard input of `make'). The first command run will always get it
3433 target. This is almost always what you want `make' to do, but it is
3521 Recursive `make' commands should always use the variable `MAKE', not
3589 The special variable `MAKEFLAGS' is always exported (unless you
3731 then `-j 1' is always put into `MAKEFLAGS' instead of the value you
3762 does not contain the command line variable definitions, and it always
3855 file from Yacc is always named `y.tab.c'. The second command moves the
4581 For example, suppose you always want the `-g' switch when you run the
5439 is unfortunate, because it means that the result does not always
5694 is always invoked (even if a `make' variable by that name also exists).
5793 The result of the `eval' function is always the empty string; thus,
6063 The exit status of `make' is always one of three values:
6234 and how to update each target. But updating the targets is not always
6425 how to make a target or prerequisite file. This will always cause an
6451 `--always-make'
6454 however, all targets so considered are always remade regardless of
6819 Here is a catalogue of predefined implicit rules which are always
6831 Not all of these rules will always be defined, even when the `-r'