autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FYI: New indexes


From: Akim Demaille
Subject: FYI: New indexes
Date: 15 Aug 2001 14:38:56 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)

Index: ChangeLog
from  Akim Demaille  <address@hidden>
        * doc/autoconf.texi (pr): New index.
        (prindex, findex): Use, merge, and output them.
        (Environment Variable Index, Output Variable Index)
        (Preprocessor Symbol Index, Autoconf Macro Index, M4 Macro Index)
        (Autotest Macro Index): Rename as...
        (Environment Variables, Output Variables,Preprocessor Symbols)
        (Autoconf Macros, M4 Macros, Autotest Macros): these.
        * doc/install.texi: Use @command.
        (Environment Variables): Rename as...
        (Defining Variables): this.

2001-08-15  Akim Demaille  <address@hidden>

Index: doc/Makefile.am
===================================================================
RCS file: /cvs/autoconf/doc/Makefile.am,v
retrieving revision 1.21
diff -u -u -r1.21 Makefile.am
--- doc/Makefile.am 2001/08/13 12:28:34 1.21
+++ doc/Makefile.am 2001/08/15 12:33:27
@@ -31,7 +31,7 @@
 CLEANFILES = autoconf.cvs \
             autoconf.ev autoconf.evs autoconf.ac autoconf.acs \
              autoconf.ov autoconf.ovs autoconf.ms autoconf.mss \
-            autoconf.at autoconf.ats \
+            autoconf.at autoconf.ats autoconf.pr autoconf.prs \
             autoconf.tmp \
             autoconf*.html standards*.html \
             autoconf*.pdf standards*.pdf
Index: doc/autoconf.texi
===================================================================
RCS file: /cvs/autoconf/doc/autoconf.texi,v
retrieving revision 1.504
diff -u -u -r1.504 autoconf.texi
--- doc/autoconf.texi 2001/08/15 12:06:30 1.504
+++ doc/autoconf.texi 2001/08/15 12:33:31
@@ -103,7 +103,14 @@
 @defcodeindex at
 @c Define an M4sugar macro index that @defmac doesn't write to.
 @defcodeindex ms
address@hidden Define an index for *foreign* programs: `mv' etc.  Used for the
address@hidden portability sections and so on.
address@hidden pr
 
address@hidden Put the programs and funcions into their own index.
address@hidden fn pr
+
+
 @node Top, Introduction, (dir), (dir)
 @comment  node-name,  next,  previous,  up
 
@@ -137,12 +144,13 @@
 * Questions::                   Questions about Autoconf, with answers
 * History::                     History of Autoconf
 * Copying This Manual::         How to make copies of this manual
-* Environment Variable Index::  Index of environment variables used
-* Output Variable Index::       Index of variables set in output files
-* Preprocessor Symbol Index::   Index of C preprocessor symbols defined
-* Autoconf Macro Index::        Index of Autoconf macros
-* M4 Macro Index::              Index of M4, M4sugar, and M4sh macros
-* Autotest Macro Index::        Index of Autotest macros
+* Environment Variables::       Index of environment variables used
+* Output Variables::            Index of variables set in output files
+* Preprocessor Symbols::        Index of C preprocessor symbols defined
+* Autoconf Macros::             Index of Autoconf macros
+* M4 Macros::                   Index of M4, M4sugar, and M4sh macros
+* Autotest Macros::             Index of Autotest macros
+* Programs and Functions::      Index of those with portability problems
 * Concept Index::               General index
 
 @detailmenu --- The Detailed Node Listing ---
@@ -356,7 +364,7 @@
 * Optional Features::           Selecting optional features
 * System Type::                 Specifying the system type
 * Sharing Defaults::            Setting site-wide defaults for @code{configure}
-* Environment Variables::       Defining environment variables.
+* Defining Variables::          Specifying the compiler etc.
 * configure Invocation::        Changing how @code{configure} runs
 * INSTALL Copyright Notice::    Copyright notice for the @file{INSTALL} file
 
@@ -472,7 +480,7 @@
 on.  @xref{The GNU build system}, for more information.
 
 Autoconf imposes some restrictions on the names of macros used with
address@hidden in C programs (@pxref{Preprocessor Symbol Index}).
address@hidden in C programs (@pxref{Preprocessor Symbols}).
 
 Autoconf requires @sc{gnu} M4 in order to generate the scripts.  It uses
 features that some @sc{unix} versions of M4, including @sc{gnu} M4 1.3,
@@ -1849,7 +1857,7 @@
 
 Some output variables are preset by the Autoconf macros.  Some of the
 Autoconf macros set additional output variables, which are mentioned in
-the descriptions for those macros.  @xref{Output Variable Index}, for a
+the descriptions for those macros.  @xref{Output Variables}, for a
 complete list of output variables.  @xref{Installation Directory
 Variables}, for the list of the preset ones related to installation
 directories.  Below are listed the other preset ones.  They all are
@@ -3229,13 +3237,14 @@
 additions, please help us keeping it as complete as possible
 
 @table @asis
-
 @item @code{sprintf}
address@hidden sprintf
 The ISO C standard says @code{sprintf} and @code{vsprintf} return the
 number of characters written, but on some old systems (SunOS for
 instance) they return the buffer pointer instead.
 
 @item @code{unlink}
address@hidden unlink
 The @sc{posix} spec says that @code{unlink} causes the given files to be
 removed only after there are no more open file handles for it.  Not all
 OS's support this behaviour though.  So even on systems that provide
@@ -7231,7 +7240,7 @@
 details.
 
 @item @command{/usr/xpg4/bin/sh} on Solaris
address@hidden @command{/usr/xpg4/bin/sh} on Solaris
address@hidden @command{/usr/xpg4/bin/sh} on Solaris
 The @sc{posix}-compliant Bourne shell on a Solaris system is
 @command{/usr/xpg4/bin/sh} and is part of an extra optional package.
 There is no extra charge for this package, but it is also not part of a
@@ -7942,7 +7951,7 @@
 
 @table @asis
 @item @command{.}
address@hidden @command{.}
address@hidden @command{.}
 Use @command{.} only with regular files (use @samp{test -f}).  Bash
 2.03, for instance, chokes on @samp{. /dev/null}.  Also, remember that
 @command{.} is not expected to look in the current directory, hence you
@@ -7967,19 +7976,19 @@
 the file was not found in the @code{$PATH}.
 
 @item @command{!}
address@hidden @command{!}
address@hidden @command{!}
 You can't use @command{!}, you'll have to rewrite your code.
 
 
 @item @command{break}
 @c ------------------
address@hidden @command{break}
address@hidden @command{break}
 The use of @samp{break 2}, etcetera, is safe.
 
 
 @item @command{case}
 @c -----------------
address@hidden @command{case}
address@hidden @command{case}
 You don't need to quote the argument; no splitting is performed.
 
 You don't need the final @samp{;;}, but you should use it.
@@ -8007,7 +8016,7 @@
 
 @item @command{echo}
 @c -----------------
address@hidden @command{echo}
address@hidden @command{echo}
 The simple @code{echo} is probably the most surprising source of
 portability troubles.  It is not possible to use @samp{echo} portably
 unless both options and escape sequences are omitted.  New applications
@@ -8040,7 +8049,7 @@
 
 @item @command{exit}
 @c -----------------
address@hidden @command{exit}
address@hidden @command{exit}
 The default value of @command{exit} is supposed to be @code{$?};
 unfortunately, some shells, such as the DJGPP port of Bash 2.04, just
 perform @samp{exit 0}.
@@ -8070,7 +8079,7 @@
 
 @item @command{export}
 @c -------------------
address@hidden @command{export}
address@hidden @command{export}
 The builtin @command{export} dubs @dfn{environment variable} a shell
 variable.  Each update of exported variables corresponds to an update of
 the environment variables.  Conversely, each environment variable
@@ -8102,14 +8111,14 @@
 
 @item @command{false}
 @c ------------------
address@hidden @command{false}
address@hidden @command{false}
 Don't expect @command{false} to exit with status 1: in the native Bourne
 shell of Solaris 8, it exits with status 255.
 
 
 @item @command{for}
 @c ----------------
address@hidden @command{for}
address@hidden @command{for}
 To loop over positional arguments, use:
 
 @example
@@ -8140,7 +8149,7 @@
 
 @item @command{if}
 @c ---------------
address@hidden @command{if}
address@hidden @command{if}
 Using @samp{!} is not portable.  Instead of:
 
 @example
@@ -8181,7 +8190,7 @@
 
 @item @command{set}
 @c ----------------
address@hidden @command{set}
address@hidden @command{set}
 This builtin faces the usual problem with arguments starting with a
 dash.  Modern shells such as Bash or Zsh understand @option{--} to specify
 the end of the options (any argument after @option{--} is a parameters,
@@ -8196,14 +8205,14 @@
 
 @item @command{shift}
 @c ------------------
address@hidden @command{shift}
address@hidden @command{shift}
 Not only is @command{shift}ing a bad idea when there is nothing left to
 shift, but in addition it is not portable: the shell of @sc{mips
 risc/os} 4.52 refuses to do it.
 
 @item @command{test}
 @c -----------------
address@hidden @command{test}
address@hidden @command{test}
 The @code{test} program is the way to perform many file and string
 tests.  It is often invoked by the alternate name @samp{[}, but using
 that name in Autoconf code is asking for trouble since it is an M4 quote
@@ -8305,7 +8314,7 @@
 
 @item @command{trap}
 @c -----------------
address@hidden @command{trap}
address@hidden @command{trap}
 It is safe to trap at least the signals 1, 2, 13 and 15.  You can also
 trap 0, i.e., have the @command{trap} run when the script ends (either via an
 explicit @command{exit}, or the end of the script).
@@ -8353,8 +8362,8 @@
 
 @item @command{true}
 @c -----------------
address@hidden @command{true}
address@hidden @command{:}
address@hidden @command{true}
address@hidden @command{:}
 Don't worry: as far as we know @command{true} is portable.
 Nevertheless, it's not always a builtin (e.g., Bash 1.x), and the
 portable shell community tends to prefer using @command{:}.  This has a
@@ -8370,7 +8379,7 @@
 
 @item @command{unset}
 @c ------------------
address@hidden @command{unset}
address@hidden @command{unset}
 You cannot assume the support of @command{unset}, nevertheless, because
 it is extremely useful to disable embarrassing variables such as
 @code{CDPATH} or @code{LANG}, you can test for its existence and use
@@ -8400,7 +8409,7 @@
 @table @asis
 @item @command{awk}
 @c ----------------
address@hidden @command{awk}
address@hidden @command{awk}
 Don't leave white spaces before the parentheses in user functions calls,
 @sc{gnu} awk will reject it:
 
@@ -8453,7 +8462,7 @@
 
 @item @command{cat}
 @c ----------------
address@hidden @command{cat}
address@hidden @command{cat}
 Don't rely on any option.  The option @option{-v}, which displays
 non-printing characters, @emph{seems} portable, though.
 
@@ -8466,7 +8475,7 @@
 
 @item @command{cmp}
 @c ----------------
address@hidden @command{cmp}
address@hidden @command{cmp}
 @command{cmp} performs a raw data comparison of two files, while
 @command{diff} compares two text files.  Therefore, if you might compare
 DOS files, even if only checking whether two files are different, use
@@ -8476,7 +8485,7 @@
 
 @item @command{cp}
 @c ---------------
address@hidden @command{cp}
address@hidden @command{cp}
 @c This is thanks to Ian.
 SunOS @command{cp} does not support @option{-f}, although its
 @command{mv} does.  It's possible to deduce why @command{mv} and
@@ -8495,7 +8504,7 @@
 
 @item @command{diff}
 @c -----------------
address@hidden @command{diff}
address@hidden @command{diff}
 Option @option{-u} is nonportable.
 
 Some implementations, such as Tru64's, fail when comparing to
@@ -8503,7 +8512,7 @@
 
 @item @command{dirname}
 @c --------------------
address@hidden @command{dirname}
address@hidden @command{dirname}
 Not all hosts have @command{dirname}, but it is reasonably easy to
 emulate, e.g.:
 
@@ -8538,7 +8547,7 @@
 
 @item @command{egrep}
 @c ------------------
address@hidden @command{egrep}
address@hidden @command{egrep}
 The empty alternative is not portable, use @samp{?} instead. For
 instance with Digital Unix v5.0:
 
@@ -8557,7 +8566,7 @@
 
 @item @command{expr}
 @c -----------------
address@hidden @command{expr}
address@hidden @command{expr}
 No @command{expr} keyword starts with @samp{x}, so use @samp{expr
 x"@var{word}" : 'address@hidden'} to keep @command{expr} from
 misinterpreting @var{word}.
@@ -8565,7 +8574,7 @@
 Don't use @code{length}, @code{substr}, @code{match} and @code{index}.
 
 @item @command{expr} (@samp{|})
address@hidden @command{expr} (@samp{|})
address@hidden @command{expr} (@samp{|})
 You can use @samp{|}.  Although @sc{posix} does require that @samp{expr
 ''} return the empty string, it does not specify the result when you
 @samp{|} together the empty string (or zero) with the empty string.  For
@@ -8592,7 +8601,7 @@
 
 @item @command{expr} (@samp{:})
 @c ----------------------------
address@hidden @command{expr}
address@hidden @command{expr}
 Don't use @samp{\?}, @samp{\+} and @samp{\|} in patterns, they are
 not supported on Solaris.
 
@@ -8660,7 +8669,7 @@
 
 @item @command{grep}
 @c -----------------
address@hidden @command{grep}
address@hidden @command{grep}
 Don't use @samp{grep -s} to suppress output, because @samp{grep -s} on
 System V does not suppress output, only error messages.  Instead,
 redirect the standard output and standard error (in case the file
@@ -8675,7 +8684,7 @@
 
 @item @command{ln}
 @c ---------------
address@hidden @command{ln}
address@hidden @command{ln}
 @cindex Symbolic links
 Don't rely on @command{ln} having a @option{-f} option.  Symbolic links
 are not available on old systems, use @samp{ln} as a fall back.
@@ -8691,7 +8700,7 @@
 
 @item @command{mv}
 @c ---------------
address@hidden @command{mv}
address@hidden @command{mv}
 @cindex Moving open files
 The only portable options are @option{-f} and @option{-i}.
 
@@ -8721,7 +8730,7 @@
 
 @item @command{sed}
 @c ----------------
address@hidden @command{sed}
address@hidden @command{sed}
 Patterns should not include the separator (unless escaped), even as part
 of a character class.  In conformance with @sc{posix}, the Cray
 @command{sed} will reject @samp{s/[^/]*$//}: use @samp{s,[^/]*$,,}.
@@ -8777,7 +8786,7 @@
 
 @item @command{sed} (@samp{t})
 @c ---------------------------
address@hidden @command{sed} (@samp{t})
address@hidden @command{sed} (@samp{t})
 Some old systems have @command{sed} that ``forget'' to reset their
 @samp{t} flag when starting a new cycle.  For instance on @sc{mips
 risc/os}, and on @sc{irix} 5.3, if you run the following @command{sed}
@@ -8851,7 +8860,7 @@
 
 @item @command{touch}
 @c ------------------
address@hidden @command{touch}
address@hidden @command{touch}
 On some old @sc{bsd} systems, @command{touch} or any command that
 results in an empty file does not update the timestamps, so use a
 command like @code{echo} as a workaround.
@@ -9585,7 +9594,7 @@
 * Optional Features::           Selecting optional features
 * System Type::                 Specifying the system type
 * Sharing Defaults::            Setting site-wide defaults for @code{configure}
-* Environment Variables::       Defining environment variables.
+* Defining Variables::          Specifying the compiler etc.
 * configure Invocation::        Changing how @code{configure} runs
 * INSTALL Copyright Notice::    Copyright notice for the @file{INSTALL} file
 @end menu
@@ -11733,7 +11742,7 @@
 
 @c ========================================================== Appendices
 
address@hidden Copying This Manual, Environment Variable Index, History, Top
address@hidden Copying This Manual, Environment Variables, History, Top
 @appendix Copying This Manual
 
 @menu
@@ -11742,7 +11751,7 @@
 
 @include fdl.texi
 
address@hidden Environment Variable Index, Output Variable Index, Copying This 
Manual, Top
address@hidden Environment Variables, Output Variables, Copying This Manual, Top
 @unnumbered Environment Variable Index
 
 This is an alphabetical list of the environment variables that Autoconf
@@ -11750,7 +11759,7 @@
 
 @printindex ev
 
address@hidden Output Variable Index, Preprocessor Symbol Index, Environment 
Variable Index, Top
address@hidden Output Variables, Preprocessor Symbols, Environment Variables, 
Top
 @unnumbered Output Variable Index
 
 This is an alphabetical list of the variables that Autoconf can
@@ -11760,7 +11769,7 @@
 
 @printindex ov
 
address@hidden Preprocessor Symbol Index, Autoconf Macro Index, Output Variable 
Index, Top
address@hidden Preprocessor Symbols, Autoconf Macros, Output Variables, Top
 @unnumbered Preprocessor Symbol Index
 
 This is an alphabetical list of the C preprocessor symbols that the
@@ -11769,7 +11778,7 @@
 
 @printindex cv
 
address@hidden Autoconf Macro Index, M4 Macro Index, Preprocessor Symbol Index, 
Top
address@hidden Autoconf Macros, M4 Macros, Preprocessor Symbols, Top
 @unnumbered Autoconf Macro Index
 
 This is an alphabetical list of the Autoconf macros.  To make the list
@@ -11777,7 +11786,7 @@
 
 @printindex ac
 
address@hidden M4 Macro Index, Autotest Macro Index, Autoconf Macro Index, Top
address@hidden M4 Macros, Autotest Macros, Autoconf Macros, Top
 @unnumbered M4 Macro Index
 
 This is an alphabetical list of the M4, M4sugar, and M4sh macros.  To
@@ -11786,15 +11795,23 @@
 
 @printindex ms
 
address@hidden Autotest Macro Index, Concept Index, M4 Macro Index, Top
address@hidden Autotest Macros, Programs and Functions, M4 Macros, Top
 @unnumbered Autotest Macro Index
 
 This is an alphabetical list of the Autotest macros.  To make the list
 easier to use, the macros are listed without their preceding @samp{AT_}.
 
 @printindex at
+
address@hidden Programs and Functions, Concept Index, Autotest Macros, Top
address@hidden Programs and Functions Index
+
+This is an alphabetical list of the programs and functions which
+portability is discussed in this document.
+
address@hidden pr
 
address@hidden Concept Index,  , Autotest Macro Index, Top
address@hidden Concept Index,  , Programs and Functions, Top
 @unnumbered Concept Index
 
 This is an alphabetical list of the files, tools, and concepts
Index: doc/install.texi
===================================================================
RCS file: /cvs/autoconf/doc/install.texi,v
retrieving revision 1.34
diff -u -u -r1.34 install.texi
--- doc/install.texi 2001/08/12 13:17:35 1.34
+++ doc/install.texi 2001/08/15 12:33:31
@@ -6,14 +6,14 @@
 
 These are generic installation instructions.
 
-The @code{configure} shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
+The @command{configure} shell script attempts to guess correct values
+for various system-dependent variables used during compilation.  It uses
 those values to create a @file{Makefile} in each directory of the
 package.  It may also create one or more @file{.h} files containing
 system-dependent definitions.  Finally, it creates a shell script
 @file{config.status} that you can run in the future to recreate the
 current configuration, and a file @file{config.log} containing compiler
-output (useful mainly for debugging @code{configure}).
+output (useful mainly for debugging @command{configure}).
 
 It can also use an optional file (typically called @file{config.cache}
 and enabled with @option{--cache-file=config.cache} or simply
@@ -22,11 +22,11 @@
 accidental use of stale cache files.)
 
 If you need to do unusual things to compile the package, please try to
-figure out how @code{configure} could check whether to do them, and mail
-diffs or instructions to the address given in the @file{README} so they
-can be considered for the next release.  If you are using the cache, and
-at some point @file{config.cache} contains results you don't want to
-keep, you may remove or edit it.
+figure out how @command{configure} could check whether to do them, and
+mail diffs or instructions to the address given in the @file{README} so
+they can be considered for the next release.  If you are using the
+cache, and at some point @file{config.cache} contains results you don't
+want to keep, you may remove or edit it.
 
 The file @file{configure.ac} (or @file{configure.in}) is used to create
 @file{configure} by a program called @code{autoconf}.  You only need
@@ -42,9 +42,9 @@
 @samp{./configure} to configure the package for your system.  If you're
 using @code{csh} on an old version of System V, you might need to type
 @samp{sh ./configure} instead to prevent @code{csh} from trying to
-execute @code{configure} itself.
+execute @command{configure} itself.
 
-Running @code{configure} takes awhile.  While running, it prints some
+Running @command{configure} takes awhile.  While running, it prints some
 messages telling which features it is checking for.
 
 @item
@@ -59,30 +59,31 @@
 documentation.
 
 @item
-You can remove the program binaries and object files from the source code
-directory by typing @samp{make clean}.  To also remove the files that
address@hidden created (so you can compile the package for a different
-kind of computer), type @samp{make distclean}.  There is also a
address@hidden maintainer-clean} target, but that is intended mainly for the
-package's developers.  If you use it, you may have to get all sorts of
-other programs in order to regenerate files that came with the distribution.
+You can remove the program binaries and object files from the source
+code directory by typing @samp{make clean}.  To also remove the files
+that @command{configure} created (so you can compile the package for a
+different kind of computer), type @samp{make distclean}.  There is also
+a @samp{make maintainer-clean} target, but that is intended mainly for
+the package's developers.  If you use it, you may have to get all sorts
+of other programs in order to regenerate files that came with the
+distribution.
 @end enumerate
 
 @node Compilers and Options
 @section Compilers and Options
 
 Some systems require unusual options for compilation or linking that the
address@hidden script does not know about.  Run @samp{./configure
address@hidden script does not know about.  Run @samp{./configure
 --help} for details on some of the pertinent environment variables.
 
-You can give @code{configure} initial values for variables by setting
+You can give @command{configure} initial values for variables by setting
 them in the environment.  You can do that on the command line like this:
 
 @example
 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
 @end example
 
address@hidden Variables}, for more details.
address@hidden Variables}, for more details.
 
 
 @node Multiple Architectures
@@ -90,18 +91,18 @@
 
 You can compile the package for more than one kind of computer at the
 same time, by placing the object files for each architecture in their
-own directory.  To do this, you must use a version of @code{make} that
-supports the @code{VPATH} variable, such as GNU @code{make}.  @code{cd}
-to the directory where you want the object files and executables to go
-and run the @code{configure} script.  @code{configure} automatically
-checks for the source code in the directory that @code{configure} is in
-and in @file{..}.
-
-If you have to use a @code{make} that does not support the @code{VPATH}
-variable, you have to compile the package for one architecture at a time
-in the source code directory.  After you have installed the package for
-one architecture, use @samp{make distclean} before reconfiguring for
-another architecture.
+own directory.  To do this, you must use a version of @command{make}
+that supports the @code{VPATH} variable, such as GNU @command{make}.
address@hidden to the directory where you want the object files and
+executables to go and run the @command{configure} script.
address@hidden automatically checks for the source code in the
+directory that @command{configure} is in and in @file{..}.
+
+If you have to use a @command{make} that does not support the
address@hidden variable, you have to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use @samp{make distclean}
+before reconfiguring for another architecture.
 
 @node Installation Names
 @section Installation Names
@@ -109,13 +110,14 @@
 By default, @samp{make install} will install the package's files in
 @file{/usr/local/bin}, @file{/usr/local/man}, etc.  You can specify an
 installation prefix other than @file{/usr/local} by giving
address@hidden the option @address@hidden
address@hidden the option @address@hidden
 
 You can specify separate installation prefixes for architecture-specific
-files and architecture-independent files.  If you give @code{configure}
-the option @address@hidden, the package will use
address@hidden as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
+files and architecture-independent files.  If you give
address@hidden the option @address@hidden, the
+package will use @var{path} as the prefix for installing programs and
+libraries.  Documentation and other data files will still use the
+regular prefix.
 
 In addition, if you use an unusual directory layout you can give options
 like @address@hidden to specify different values for
@@ -123,32 +125,33 @@
 the directories you can set and what kinds of files go in them.
 
 If the package supports it, you can cause programs to be installed with
-an extra prefix or suffix on their names by giving @code{configure} the
-option @address@hidden or
+an extra prefix or suffix on their names by giving @command{configure}
+the option @address@hidden or
 @address@hidden
 
 @node Optional Features
 @section Optional Features
 
 Some packages pay attention to @address@hidden options
-to @code{configure}, where @var{feature} indicates an optional part of
-the package.  They may also pay attention to
+to @command{configure}, where @var{feature} indicates an optional part
+of the package.  They may also pay attention to
 @address@hidden options, where @var{package} is something
 like @samp{gnu-as} or @samp{x} (for the X Window System).  The
 @file{README} should mention any @option{--enable-} and @option{--with-}
 options that the package recognizes.
 
-For packages that use the X Window System, @code{configure} can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the @code{configure} options @address@hidden
-and @address@hidden to specify their locations.
+For packages that use the X Window System, @command{configure} can
+usually find the X include and library files automatically, but if it
+doesn't, you can use the @command{configure} options
address@hidden@var{dir}} and @address@hidden to
+specify their locations.
 
 @node System Type
 @section Specifying the System Type
 
-There may be some features @code{configure} cannot figure out
+There may be some features @command{configure} cannot figure out
 automatically, but needs to determine by the type of host the package
-will run on.  Usually @code{configure} can figure that out, but if it
+will run on.  Usually @command{configure} can figure that out, but if it
 prints a message saying it cannot guess the host type, give it the
 @address@hidden option.  @var{type} can either be a short
 name for the system type, such as @samp{sun4}, or a canonical name which
@@ -162,17 +165,16 @@
 where @var{system} can have one of these forms:
 
 @example
address@hidden
address@hidden@var{os}
address@hidden @address@hidden
 @end example
 
 See the file @file{config.sub} for the possible values of each field.
 If @file{config.sub} isn't included in this package, then this package
 doesn't need to know the host type.
 
-If you are @emph{building} compiler tools for cross-compiling, you should
-use the @address@hidden option to select the type of system
-they will produce code for.
+If you are @emph{building} compiler tools for cross-compiling, you
+should use the @address@hidden option to select the type of
+system they will produce code for.
 
 If you want to @emph{use} a cross compiler, that generates code for a
 platform different from the build platform, you should specify the host
@@ -186,25 +188,25 @@
 @node Sharing Defaults
 @section Sharing Defaults
 
-If you want to set default values for @code{configure} scripts to share,
-you can create a site shell script called @file{config.site} that gives
-default values for variables like @code{CC}, @code{cache_file}, and
address@hidden  @code{configure} looks for
+If you want to set default values for @command{configure} scripts to
+share, you can create a site shell script called @file{config.site} that
+gives default values for variables like @code{CC}, @code{cache_file},
+and @code{prefix}.  @command{configure} looks for
 @address@hidden/share/config.site} if it exists, then
 @address@hidden/etc/config.site} if it exists.  Or, you can set the
 @code{CONFIG_SITE} environment variable to the location of the site
-script.  A warning: not all @code{configure} scripts look for a site
+script.  A warning: not all @command{configure} scripts look for a site
 script.
 
address@hidden Environment Variables
address@hidden Environment Variables
address@hidden Defining Variables
address@hidden Defining Variables
 
 Variables not defined in a site shell script can be set in the
-environment passed to configure.  However, some packages may run
-configure again during the build, and the customized values of these
+environment passed to @command{configure}.  However, some packages may
+run configure again during the build, and the customized values of these
 variables may be lost.  In order to avoid this problem, you should set
-them in the @code{configure} command line, using @samp{VAR=value}.  For
-example:
+them in the @command{configure} command line, using @samp{VAR=value}.
+For example:
 
 @example
 ./configure CC=/usr/local2/bin/gcc
@@ -216,19 +218,19 @@
 
 
 @node configure Invocation
address@hidden @code{configure} Invocation
address@hidden @command{configure} Invocation
 
address@hidden recognizes the following options to control how it
address@hidden recognizes the following options to control how it
 operates.
 
 @table @option
 @item --help
 @itemx -h
-Print a summary of the options to @code{configure}, and exit.
+Print a summary of the options to @command{configure}, and exit.
 
 @item --version
 @itemx -V
-Print the version of Autoconf used to generate the @code{configure}
+Print the version of Autoconf used to generate the @command{configure}
 script, and exit.
 
 @item address@hidden
@@ -250,17 +252,18 @@
 
 @item address@hidden
 Look for the package's source code in directory @var{dir}.  Usually
address@hidden can determine that directory automatically.
address@hidden can determine that directory automatically.
 @end table
 
 @noindent
address@hidden also accepts some other, not widely useful, options.
address@hidden also accepts some other, not widely useful, options.
 Run @samp{configure --help} for more details.
 
 @node INSTALL Copyright Notice
 @section Copyright Notice for the @file{INSTALL} File
 
-Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, Inc.
+Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation,
+Inc.
 
 The @file{INSTALL} file is free documentation; the Free Software
 Foundation gives unlimited permission to copy, distribute and modify it.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]