Mercurial > hg > CbC > CbC_gcc

comparison gcc/doc/makefile.texi @ 63:b7f97abdc517 gcc-4.6-20100522

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
update gcc from gcc-4.5.0 to gcc-4.6
author ryoma <e075725@ie.u-ryukyu.ac.jp>
date Mon, 24 May 2010 12:47:05 +0900
parents a06113de4d67
children f6334be47118
comparison
equal deleted inserted replaced
56:3c8a44c06a95 63:b7f97abdc517
1 @c Copyright (C) 2001, 2002, 2003, 2004, 2006, 2008 1 @c Copyright (C) 2001, 2002, 2003, 2004, 2006, 2008, 2010
2 @c Free Software Foundation, Inc. 2 @c Free Software Foundation, Inc.
3 @c This is part of the GCC manual. 3 @c This is part of the GCC manual.
4 @c For copying conditions, see the file gcc.texi. 4 @c For copying conditions, see the file gcc.texi.
5 5
6 @node Makefile 6 @node Makefile
44 That, and all the files created by @command{configure}. 44 That, and all the files created by @command{configure}.
45 45
46 @item maintainer-clean 46 @item maintainer-clean
47 Distclean plus any file that can be generated from other files. Note 47 Distclean plus any file that can be generated from other files. Note
48 that additional tools may be required beyond what is normally needed to 48 that additional tools may be required beyond what is normally needed to
49 build gcc. 49 build GCC.
50 50
51 @item srcextra 51 @item srcextra
52 Generates files in the source directory that do not exist in CVS but 52 Generates files in the source directory that are not version-controlled but
53 should go into a release tarball. One example is @file{gcc/java/parse.c} 53 should go into a release tarball.
54 which is generated from the CVS source file @file{gcc/java/parse.y}.
55 54
56 @item srcinfo 55 @item srcinfo
57 @itemx srcman 56 @itemx srcman
58 Copies the info-formatted and manpage documentation into the source 57 Copies the info-formatted and manpage documentation into the source
59 directory usually for the purpose of generating a release tarball. 58 directory usually for the purpose of generating a release tarball.
60 59
61 @item install 60 @item install
62 Installs gcc. 61 Installs GCC.
63 62
64 @item uninstall 63 @item uninstall
65 Deletes installed files. 64 Deletes installed files, though this is not supported.
66 65
67 @item check 66 @item check
68 Run the testsuite. This creates a @file{testsuite} subdirectory that 67 Run the testsuite. This creates a @file{testsuite} subdirectory that
69 has various @file{.sum} and @file{.log} files containing the results of 68 has various @file{.sum} and @file{.log} files containing the results of
70 the testing. You can run subsets with, for example, @samp{make check-gcc}. 69 the testing. You can run subsets with, for example, @samp{make check-gcc}.
71 You can specify specific tests by setting RUNTESTFLAGS to be the name 70 You can specify specific tests by setting @env{RUNTESTFLAGS} to be the name
72 of the @file{.exp} file, optionally followed by (for some tests) an equals 71 of the @file{.exp} file, optionally followed by (for some tests) an equals
73 and a file wildcard, like: 72 and a file wildcard, like:
74 73
75 @smallexample 74 @smallexample
76 make check-gcc RUNTESTFLAGS="execute.exp=19980413-*" 75 make check-gcc RUNTESTFLAGS="execute.exp=19980413-*"
77 @end smallexample 76 @end smallexample
78 77
79 Note that running the testsuite may require additional tools be 78 Note that running the testsuite may require additional tools be
80 installed, such as TCL or dejagnu. 79 installed, such as Tcl or DejaGnu.
81 @end table 80 @end table
82 81
83 The toplevel tree from which you start GCC compilation is not 82 The toplevel tree from which you start GCC compilation is not
84 the GCC directory, but rather a complex Makefile that coordinates 83 the GCC directory, but rather a complex Makefile that coordinates
85 the various steps of the build, including bootstrapping the compiler 84 the various steps of the build, including bootstrapping the compiler