-Installing GAS
-==============
-
-GAS comes with a `configure' script that automates the process of preparing
-GAS for installation; you can then use `make' to build the program.
-
-The GAS distribution includes all the source code you need for GAS in a single
-directory, the name of which is usually composed by appending the version
-number to `gas'.
-
-The simplest way to configure and build GAS is to run `configure' from the
-`gas-VERSION-NUMBER' source directory, which in this example is the `gas-2.2.1'
-directory.
-
-First switch to the `gas-VERSION-NUMBER' source directory if you are not
-already in it; then run `configure'. Pass the identifier for the platform on
-which GAS will run as an argument. For example:
-
- cd gas-2.2.1
- ./configure HOST
- make
-
-where HOST is an identifier such as `sun4' or `decstation', that identifies
-the platform where GAS will run.
-
-Running `configure HOST' followed by `make' builds the `bfd', `opcode', and
-`libiberty' libraries, then `gas' itself. (Exception: For VMS, the `bfd'
-library is not used.) The configured source files, and the binaries, are left
-in the corresponding source directories.
-
-The `configure' program is a Bourne-shell (`/bin/sh') script; if your system
-does not recognize this automatically when you run a different shell, you may
-need to run `sh' on it explicitly:
-
- sh configure HOST
-
-If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gas-2.2.1'
-source directory for version 2.2.1, `configure' creates configuration
-files for every directory level underneath (unless you tell it not to,
-with the `--norecursion' option).
-
-You can run the `configure' script from any of the subordinate directories in
-the GAS distribution, if you only want to configure that subdirectory; but be
-sure to specify a path to it.
-
-For example, with version 2.2.1, type the following to configure only the `bfd'
-subdirectory:
-
- cd gas-2.2.1/bfd
- ../configure HOST
-
-Compiling GAS in another directory
-==================================
-
- If you want to run GAS versions for several host or target machines,
-you need a different `gas' compiled for each combination of host and
-target. `configure' is designed to make this easy by allowing you to
-generate each configuration in a separate subdirectory, rather than in
-the source directory. If your `make' program handles the `VPATH'
-feature (GNU `make' does), running `make' in each of these directories
-builds the `gas' program specified there.
-
- To build `gas in a separate directory, run `configure' with the
-`--srcdir' option to specify where to find the source. (You also need
-to specify a path to find `configure' itself from your working
-directory. If the path to `configure' would be the same as the
-argument to `--srcdir', you can leave out the `--srcdir' option; it
-will be assumed.)
-
- For example, with version 2.2.1, you can build GAS in a separate
-directory for a Sun 4 like this:
-
- cd gas-2.2.1
- mkdir ../gas-sun4
- cd ../gas-sun4
- ../gas-2.2.1/configure sun4
- make
-
- When `configure' builds a configuration using a remote source
-directory, it creates a tree for the binaries with the same structure
-(and using the same names) as the tree under the source directory. In
-the example, you'd find the Sun 4 library `libiberty.a' in the
-directory `gas-sun4/libiberty', and GAS itself in `gas-sun4/gas'.
-
- One popular reason to build several GAS configurations in separate
-directories is to configure GAS for cross-compiling (where GAS runs on
-one machine--the host--while debugging programs that run on another
-machine--the target). You specify a cross-debugging target by giving
-the `--target=TARGET' option to `configure'.
-
- When you run `make' to build a program or library, you must run it
-in a configured directory--whatever directory you were in when you
-called `configure' (or one of its subdirectories).
-
- The `Makefile' that `configure' generates in each source directory
-also runs recursively. If you type `make' in a source directory such
-as `gas-2.2.1' (or in a separate configured directory configured with
-`--srcdir=PATH/gas-2.2.1'), you will build all the required libraries,
-and then build GAS.
-
- When you have multiple hosts or targets configured in separate
-directories, you can run `make' on them in parallel (for example, if
-they are NFS-mounted on each of the hosts); they will not interfere
-with each other.
-
-