diff options
Diffstat (limited to 'contrib/gcc/doc/makefile.texi')
-rw-r--r-- | contrib/gcc/doc/makefile.texi | 58 |
1 files changed, 42 insertions, 16 deletions
diff --git a/contrib/gcc/doc/makefile.texi b/contrib/gcc/doc/makefile.texi index 1e64c5e..4e91214 100644 --- a/contrib/gcc/doc/makefile.texi +++ b/contrib/gcc/doc/makefile.texi @@ -1,4 +1,4 @@ -@c Copyright (C) 2001, 2002 Free Software Foundation, Inc. +@c Copyright (C) 2001, 2002, 2003, 2004 Free Software Foundation, Inc. @c This is part of the GCC manual. @c For copying conditions, see the file gcc.texi. @@ -13,9 +13,17 @@ This is the default target. Depending on what your build/host/target configuration is, it coordinates all the things that need to be built. @item doc -Produce info-formatted documentation. Also, @samp{make dvi} is -available for DVI-formatted documentation, and @samp{make -generated-manpages} to generate man pages. +Produce info-formatted documentation and man pages. Essentially it +calls @samp{make man} and @samp{make info}. + +@item dvi +Produce DVI-formatted documentation. + +@item man +Generate man pages. + +@item info +Generate info-formatted pages. @item mostlyclean Delete the files made while building the compiler. @@ -26,14 +34,21 @@ That, and all the other files built by @samp{make all}. @item distclean That, and all the files created by @command{configure}. -@item extraclean -That, and any temporary or intermediate files, like emacs backup files. - @item maintainer-clean Distclean plus any file that can be generated from other files. Note that additional tools may be required beyond what is normally needed to build gcc. +@item srcextra +Generates files in the source directory that do not exist in CVS but +should go into a release tarball. One example is @file{gcc/c-parse.c} +which is generated from the CVS source file @file{gcc/c-parse.in}. + +@item srcinfo +@itemx srcman +Copies the info-formatted and manpage documentation into the source +directory usually for the purpose of generating a release tarball. + @item install Installs gcc. @@ -56,7 +71,7 @@ Note that running the testsuite may require additional tools be installed, such as TCL or dejagnu. @item bootstrap -Builds gcc three times---once with the native compiler, once with the +Builds GCC three times---once with the native compiler, once with the native-built compiler it just built, and once with the compiler it built the second time. In theory, the last two should produce the same results, which @samp{make compare} can check. Each step of this process @@ -68,21 +83,25 @@ Like @code{bootstrap}, except that the various stages are removed once they're no longer needed. This saves disk space. @item bubblestrap -Once bootstrapped, this incrementally rebuilds each of the three stages, -one at a time. It does this by ``bubbling'' the stages up from their -subdirectories, rebuilding them, and copying them back to their -subdirectories. This will allow you to, for example, quickly rebuild a -bootstrapped compiler after changing the sources, without having to do a -full bootstrap. +This incrementally rebuilds each of the three stages, one at a time. +It does this by ``bubbling'' the stages up from their subdirectories +(if they had been built previously), rebuilding them, and copying them +back to their subdirectories. This will allow you to, for example, +continue a bootstrap after fixing a bug which causes the stage2 build +to crash. @item quickstrap Rebuilds the most recently built stage. Since each stage requires -special invocation, using this target means you don't have to keep track -of which stage you're on or what invocation that stage needs. +special invocation, using this target means you don't have to keep +track of which stage you're on or what invocation that stage needs. @item cleanstrap Removed everything (@samp{make clean}) and rebuilds (@samp{make bootstrap}). +@item restrap +Like @code{cleanstrap}, except that the process starts from the first +stage build, not from scratch. + @item stage@var{N} (@var{N} = 1@dots{}4) For each stage, moves the appropriate files to the @file{stage@var{N}} subdirectory. @@ -99,4 +118,11 @@ Compares the results of stages 2 and 3. This ensures that the compiler is running properly, since it should produce the same object files regardless of how it itself was compiled. +@item profiledbootstrap +Builds a compiler with profiling feedback information. For more +information, see +@ref{Building,,Building with profile feedback,gccinstall,Installing GCC}. +This is actually a target in the top-level directory, which then +recurses into the @file{gcc} subdirectory multiple times. + @end table |