summaryrefslogtreecommitdiff
path: root/gcc/doc/makefile.texi
diff options
context:
space:
mode:
authorKelley Cook <kcook@gcc.gnu.org>2004-02-06 01:14:32 +0000
committerR. Kelley Cook <kcook@gcc.gnu.org>2004-02-06 01:14:32 +0000
commitce5c1cf3100417ef1c66e3c0caafc3b95e28848c (patch)
tree0b801a095b5fb310239b09469dbfe374641e7e8d /gcc/doc/makefile.texi
parent02ba6b2254446cc434f56b1e2bc6623220963a7d (diff)
downloadgcc-ce5c1cf3100417ef1c66e3c0caafc3b95e28848c.tar.gz
install.texi: Update automake and autoconf version requirements.
2004-02-05 Kelley Cook <kcook@gcc.gnu.org> * doc/install.texi: Update automake and autoconf version requirements. Note where to find gcj automake version. 2004-02-05 Kelley Cook <kcook@gcc.gnu.org> * Makefile.in (generate-manpages): Move dependencies to ... (man): here. * doc/makefile.texi: Document new targets. * doc/sourcebuild.texi (Make-lang.in): Document new langhooks. From-SVN: r77365
Diffstat (limited to 'gcc/doc/makefile.texi')
-rw-r--r--gcc/doc/makefile.texi24
1 files changed, 21 insertions, 3 deletions
diff --git a/gcc/doc/makefile.texi b/gcc/doc/makefile.texi
index 1995e5824a3..d39baa5f1ae 100644
--- a/gcc/doc/makefile.texi
+++ b/gcc/doc/makefile.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.
@@ -31,6 +39,16 @@ 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.