[patch] use @command in makefile.texi

[Matt Kraai <kraai at alumni dot cmu dot edu>]

Howdy,

In makefile.texi, commands were tagged with @code instead of
@command.  I tested the following patch with "make info" and
"make dvi" on powerpc-unknown-linux-gnu.  OK to commit?

      * doc/makefile.texi: Use @command instead of @code for
      commands.

Index: gcc/doc/makefile.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/makefile.texi,v
retrieving revision 1.3
diff -c -3 -p -r1.3 makefile.texi
*** gcc/doc/makefile.texi	4 Sep 2002 17:35:59 -0000	1.3
--- gcc/doc/makefile.texi	31 Mar 2003 14:26:10 -0000
*************** This is the default target.  Depending o
*** 13,30 ****
  configuration is, it coordinates all the things that need to be built.
  
  @item doc
! Produce info-formatted documentation.  Also, @code{make dvi} is
! available for DVI-formatted documentation, and @code{make
  generated-manpages} to generate man pages.
  
  @item mostlyclean
  Delete the files made while building the compiler.
  
  @item clean
! That, and all the other files built by @code{make all}.
  
  @item distclean
! That, and all the files created by @code{configure}.
  
  @item extraclean
  That, and any temporary or intermediate files, like emacs backup files.
--- 13,30 ----
  configuration is, it coordinates all the things that need to be built.
  
  @item doc
! Produce info-formatted documentation.  Also, @command{make dvi} is
! available for DVI-formatted documentation, and @command{make
  generated-manpages} to generate man pages.
  
  @item mostlyclean
  Delete the files made while building the compiler.
  
  @item clean
! That, and all the other files built by @command{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.
*************** Deletes installed files.
*** 43,49 ****
  @item check
  Run the testsuite.  This creates a @file{testsuite} subdirectory that
  has various @file{.sum} and @file{.log} files containing the results of
! the testing.  You can run subsets with, for example, @code{make check-gcc}.
  You can specify specific tests by setting RUNTESTFLAGS to be the name
  of the @file{.exp} file, optionally followed by (for some tests) an equals
  and a file wildcard, like:
--- 43,49 ----
  @item check
  Run the testsuite.  This creates a @file{testsuite} subdirectory that
  has various @file{.sum} and @file{.log} files containing the results of
! the testing.  You can run subsets with, for example, @command{make check-gcc}.
  You can specify specific tests by setting RUNTESTFLAGS to be the name
  of the @file{.exp} file, optionally followed by (for some tests) an equals
  and a file wildcard, like:
*************** installed, such as TCL or dejagnu.
*** 59,65 ****
  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 @code{make compare} can check.  Each step of this process
  is called a ``stage'', and the results of each stage @var{N}
  (@var{N} = 1 at dots{}3) are copied to a subdirectory @file{stage at var{N}/}.
  
--- 59,65 ----
  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 @command{make compare} can check.  Each step of this process
  is called a ``stage'', and the results of each stage @var{N}
  (@var{N} = 1 at dots{}3) are copied to a subdirectory @file{stage at var{N}/}.
  
*************** special invocation, using this target me
*** 81,87 ****
  of which stage you're on or what invocation that stage needs.
  
  @item cleanstrap
! Removed everything (@code{make clean}) and rebuilds (@code{make bootstrap}).
  
  @item stage at var{N} (@var{N} = 1 at dots{}4)
  For each stage, moves the appropriate files to the @file{stage at var{N}}
--- 81,88 ----
  of which stage you're on or what invocation that stage needs.
  
  @item cleanstrap
! Removed everything (@command{make clean}) and rebuilds (@command{make
! bootstrap}).
  
  @item stage at var{N} (@var{N} = 1 at dots{}4)
  For each stage, moves the appropriate files to the @file{stage at var{N}}

Matt
-- 
It's most certainly GNU/Linux, not Linux.  Read more at
http://www.gnu.org/gnu/why-gnu-linux.html.