Lines Matching refs:always

434 or unusual tools in your commands: you can almost always emulate what
1334 to this variable will be ignored; it will always return its special
1419 commands but no prerequisites, that file will always be remade
1443 a makefile is not always necessary.@refill
1593 A rule is always expanded the same way, regardless of the form:
1601 and the commands used to construct the target are always deferred.  This
1672 always take place within the scope of the automatic variables for that
1750 the rule with the command script is always evaluated last.
2452 always used whether or not the target needs to be built.  Thus, if the
2680 the subdirectory obviously always exists; otherwise it won't be built)
2764 depending on this one will always have their commands run.
2967 are always low resolution.  You need not list archive members as
3325 If there are no prerequisites for that rule, its commands are always
3365 makefile.  And, you must always be very careful to update the makefile
3404 regenerate the prerequisites, because it always regenerates any makefile
3499 always interpreted by @file{/bin/sh} unless the makefile specifies
3878 @code{COMSPEC} (which is always set) is used instead.
3972 input of @code{make}).  The first command run will always get it first, and
4117 as a target.  This is almost always what you want @code{make} to do, but
4215 Recursive @code{make} commands should always use the variable @code{MAKE},
4302 The special variable @code{MAKEFLAGS} is always exported (unless you
4507 @samp{-j 1} is always put into @code{MAKEFLAGS} instead of the value you
4549 does not contain the command line variable definitions, and it always
4671 always named @file{y.tab.c}.  The second command moves the output to the
5601 For example, suppose you always want the @samp{-g} switch when you run the
6660 unfortunate, because it means that the result does not always have the
6972 is always invoked (even if a @code{make} variable by that name also
7092 The result of the @code{eval} function is always the empty string;
7421 The exit status of @code{make} is always one of three values:
7613 and how to update each target.  But updating the targets is not always
7854 or prerequisite file.  This will always cause an error message, but
7883 @itemx --always-make
7884 @cindex @code{--always-make}
7887 however, all targets so considered are always remade regardless of the
8337 Here is a catalogue of predefined implicit rules which are always
8349 Not all of these rules will always be defined, even when the @samp{-r}
9044 prerequisites actually exist or are mentioned always takes priority over a
9245 @samp{D} variants all omit the trailing slash which always appears in
10229 strings.  We feel it is much cleaner to always use automatic variables
10278 We feel that it is cleaner for a rule without commands to always simply
10711 must always be associated with a target.