* Multiple Architectures:: Compiling for multiple architectures at once
* Installation Names:: Installing in different directories
* Optional Features:: Selecting optional features
-* Particular Systems:: Particular systems
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
* Multiple Architectures:: Compiling for multiple architectures at once
* Installation Names:: Installing in different directories
* Optional Features:: Selecting optional features
-* Particular Systems:: Particular systems
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
@item
Most tests which produce their result in a substituted variable allow to
override the test by setting the variable on the @command{configure}
-command line (@pxref{Compilers and Options}, @pxref{Defining Variables},
-@pxref{Particular Systems}).
+command line (@pxref{Compilers and Options}, @pxref{Defining Variables}).
@item
Many tests store their result in a cache variable (@pxref{Caching
the installation locations.
@item --build=@var{type}
-Build for architecture @var{type}. @ref{Specifying the System Type}
+Build for architecture @var{type}. @ref{System Type}.
for more details, including other system type options.
@item --enable-@var{feature}