install.texi: remove irrelevant sections

Remove "Multiple Architectures" and "Particular Systems" sections using
the following filter script:

awk '/^@node (Multiple Architectures|Particular Systems)/{skip=1;next}
/^@node/{skip=0} {if(!skip)print}'

* install.texi (Multiple Architectures, Particular Systems): Remove.

install.texi

@@ -1,4 +1,4 @@
-@c This file is included by autoconf.texi and is used to produce
+@c This file is imported from GNU Autoconf and edited to produce
 @c the INSTALL file.
 
 @ifclear autoconf
@@ -130,40 +130,6 @@ Here is an example:
 @xref{Defining Variables}, for more details.
 
 
-@node Multiple Architectures
-@section Compiling For Multiple Architectures
-
-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 can use GNU @command{make}.
-@command{cd} to the directory where you want the object files and
-executables to go and run the @command{configure} script.
-@command{configure} automatically checks for the source code in the
-directory that @command{configure} is in and in @file{..}.  This is
-known as a @dfn{VPATH} build.
-
-With a non-GNU @command{make},
-it is safer 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.
-
-On MacOS X 10.5 and later systems, you can create libraries and
-executables that work on multiple system types---known as @dfn{fat} or
-@dfn{universal} binaries---by specifying multiple @option{-arch} options
-to the compiler but only a single @option{-arch} option to the
-preprocessor.  Like this:
-
-@example
-./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-            CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-            CPP="gcc -E" CXXCPP="g++ -E"
-@end example
-
-This is not guaranteed to produce working output in all cases, you may
-have to build one architecture at a time and combine the results
-using the @command{lipo} tool if you have problems.
-
 @node Installation Names
 @section Installation Names
 
@@ -248,53 +214,6 @@ output, which can be overridden with @code{make V=1}; while running
 @samp{./configure --disable-silent-rules} sets the default to verbose,
 which can be overridden with @code{make V=0}.
 
-@node Particular Systems
-@section Particular systems
-
-On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC is
-not installed, it is recommended to use the following options in order to
-use an ANSI C compiler:
-
-@example
-./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
-@end example
-
-@noindent
-and if that doesn't work, install pre-built binaries of GCC for HP-UX.
-
-HP-UX @command{make} updates targets which have the same time stamps as
-their prerequisites, which makes it generally unusable when shipped
-generated files such as @command{configure} are involved.  Use GNU
-@command{make} instead.
-
-On OSF/1 a.k.a.@: Tru64, some versions of the default C compiler cannot
-parse its @code{<wchar.h>} header file.  The option @option{-nodtk} can be
-used as a workaround.  If GNU CC is not installed, it is therefore
-recommended to try
-
-@example
-./configure CC="cc"
-@end example
-
-@noindent
-and if that doesn't work, try
-
-@example
-./configure CC="cc -nodtk"
-@end example
-
-On Solaris, don't put @code{/usr/ucb} early in your @env{PATH}.  This
-directory contains several dysfunctional programs; working variants
-of these programs are available in @code{/usr/bin}.  So, if you need
-@code{/usr/ucb} in your @env{PATH}, put it @emph{after} @code{/usr/bin}.
-
-On Haiku, software installed for all users goes in @file{/boot/common},
-not @file{/usr/local}.  It is recommended to use the following options:
-
-@example
-./configure --prefix=/boot/common
-@end example
-
 @node System Type
 @section Specifying the System Type