Lines Matching refs:update

102 * Archives::                    How @code{make} can update library archives.
325 * Archive Symbols::             How to update archive symbol directories.
540 the commands on the prerequisites to create or update the target.  A
627 prerequisites.  These shell commands say how to update the target file.
631 work.  It is up to you to supply commands that will update the target
660 update.    You can override this behavior using the command line
669 update the executable program @file{edit}; therefore, we put that rule
684 processed according to its own rule.  These rules say to update each
700 files.  But @code{make} would update automatically generated C programs,
711 @code{make} will compile that file to update @file{insert.o}, and then
963 may also give commands to use to create or update the targets.
972 update such a target.  @xref{Implicit Rules, ,Using Implicit Rules}.
1401 each as a goal target and attempt to update it.  If a makefile has a
1402 rule which says how to update it (found either in that very makefile or
1407 again.  (It will also attempt to update each of them over again, but
1453 Thus, @samp{make -f mfile -n foo} will update @file{mfile}, read it in,
1454 and then print the commands to update @file{foo} and its prerequisites
1465 @file{mfile}, print the commands needed to update it without actually
1466 running them, and then print the commands needed to update @file{foo}
1612 distinct phases: a read-in phase and a target-update phase
1817 @dfn{commands} to use to create or update the target.
1884 How to update the file @file{foo.o}: by running @code{cc} as stated.
1948 and how to update them when necessary.
1962 How to update is specified by @var{commands}.  These are lines to be
2704 is, its commands are run every time @code{make} goes to update that
2801 does so because one of the commands is a @code{touch} command to update the
3338 provide a mechanism for cases in which the method used to update a target
3339 differs depending on which prerequisite files caused the update, and such
3365 makefile.  And, you must always be very careful to update the makefile
3798 When it is time to execute commands to update a target, they are
4112 date, so the next time @code{make} runs, it will not try to update that
4131 delete the target file that the command was supposed to update.  This is
7413 But you might want to update only some of the files; you might want to use
7474 to update.  Other targets are updated as well if they appear as
7613 and how to update each target.  But updating the targets is not always
8274 will automatically look for an implicit rule that tells how to update it.
8897 reason to update that target.
8900 in order to update something else, it deletes @var{b} later on after it
9707 update status as the file @var{t}.
9746 Therefore, valid commands to update an archive member target probably must
9793 into the archive.  For example, it will update the archive member target
9831 * Archive Symbols::             How to update archive symbol directories.
9844 names defined by all the other members.  After you update any other
9845 members, you need to update @file{__.SYMDEF} so that it will summarize the
9862 The effect of this is to update archive members @file{x.o}, @file{y.o},
9863 etc., and then update the symbol directory member @file{__.SYMDEF} by
9874 @cindex parallel execution, and archive update
9876 @cindex @code{-j}, and archive update
9904 For example, here is the old-fashioned suffix rule to update a library
10964         getoldopt.c update.c gnu.c mangle.c
10970         getoldopt.o update.o gnu.o mangle.o