Datasheet

the emacs editor. The benefit of the info system is that you can navigate the documentation using links
and cross-references to jump directly to relevant sections. For the documentation author, the
info system
has the benefit that its files can be automatically generated from the same source as the printed, typeset
documentation.
Try It Out Manual Pages and info
Let’s look for documentation of the GNU C compiler (gcc).
1. First take a look at the manual page.
$ man gcc
GCC(1) GNU GCC(1)
NAME
gcc - GNU project C and C++ compiler
SYNOPSIS
gcc [-c|-S|-E] [-std=standard]
[-g] [-pg] [-Olevel]
[-Wwarn...] [-pedantic]
[-Idir...] [-Ldir...]
[-Dmacro[=defn]...] [-Umacro]
[-foption...] [-mmachine-option...]
[-o outfile] infile...
Only the most useful options are listed here; see below
for the remainder. g++ accepts mostly the same options as
gcc.
DESCRIPTION
When you invoke GCC, it normally does preprocessing, com
pilation, assembly and linking. The ``overall options’‘
allow you to stop this process at an intermediate stage.
For example, the -c option says not to run the linker.
Then the output consists of object files output by the
assembler.
Other options are passed on to one stage of processing.
Some options control the preprocessor and others the com
piler itself. Yet other options control the assembler and
linker; most of these are not documented here, since we
rarely need to use any of them.
...
If you want, you can read about the options that the compiler supports. The manual page in this case is
quite long, but it forms only a small part of the total documentation for GNU C (and C++).
When reading manual pages, you can use the spacebar to read the next page, Enter (or Return if your
keyboard has that key instead) to read the next line, and q to quit altogether.
15
Chapter 1: Getting Started
47627c01.qxd:WroxPro 9/28/07 8:56 PM Page 15