			TO INSTALL THIS PACKAGE

USING DEFAULTS:

Execute commands similar to the following (note: the following commands
log the installation process and allow you to view it at the same time):

    Using csh(1) or tcsh(1):
	% (./configure && make all install clean) >&! log &
	% tail -f log

    Using a POSIX.2 shell (e.g. sh, bash, or ksh):
	$ (./configure && make all install clean) > log 2>&1 &
	$ tail -f log

By default, an optimized version of the software will be built using the
compilers referenced by your PATH environment variable.  Futhermore, the
software will be installed in peer directories of the directory containing
this file (e.g. in `../bin/', `../lib/', etc.).  If this is unsatisfactory,
then see the next section.


USING CUSTOMIZATIONS:

1.  Configure the package for your system.  In the directory that this
file is in, type `./configure'.  If you're using `csh' on an old
version of System V, you might need to type `sh configure' instead to
prevent `csh' from trying to execute `configure' itself.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the Makefile(s) (one in each subdirectory of the source
directory).  In some packages it creates a C header file containing
system-dependent definitions.  It also creates a file `config.status'
that you can run in the future to recreate the current configuration.

Running `configure' takes a minute or two.  While it is running, it
prints some messages that tell what it is doing.  If you don't want to
see the messages, run `configure' with its standard output redirected
to `/dev/null'; for example, `./configure >/dev/null'.

By default, `make install' will install the package's files in ../bin,
../lib, ../man, etc., relative to the directory containing this file.
You can specify an installation prefix other than /usr/local by giving
`configure' the option `--prefix=PATH'.  Alternately, you can do so by
changing the `prefix' variable in the Makefile that `configure' creates
(the Makefile in the top-level directory, if the package contains
subdirectories).

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If
you give `configure' the option `--exec_prefix=PATH', the package will
use PATH as the prefix for installing programs and libraries.  Data
files and documentation will still use the regular prefix.  Normally,
all files are installed using the regular prefix.

You can tell `configure' to figure out the configuration for your
system, and record it in `config.status', without actually configuring
the package (creating `Makefile's and perhaps a configuration header
file).  To do this, give `configure' the `--no-create' option.  Later,
you can run `./config.status' to actually configure the package.  This
option is useful mainly in `Makefile' rules for updating `config.status'
and `Makefile'.  You can also give `config.status' the `--recheck'
option, which makes it re-run `configure' with the same arguments you
used before.  This is useful if you change `configure'.

`configure' ignores any other arguments that you give it.

If your system requires unusual options for compilation or linking
that `configure' doesn't know about, you can give `configure' initial
values for some variables by setting them in the environment.  In
Bourne-compatible shells, you can do that on the command line like
this:
	CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure

The `make' variables that you might want to override with environment
variables when running `configure' are:

    CC		C compiler program.  Default is system-dependent.

    CPPFLAGS	Additional C preprocessor options (e.g. `-Dfoo -Dbar ...').

    CFLAGS	Additional C compiler options (e.g. `-g').

    FFLAGS	Additional FORTRAN compiler options (e.g. `-g').

    LIBS	Additional libraries to link against (e.g.  
		`-lfoo -lbar ...').

    PERL	Pathname of the perl utility.  If set to the empty
		string, then the top-level makefile will ignore the
		UDUNITS extension module in the perl/ subdirectory.  If,
		however, it is set to a non-empty string, or the
		configure script finds the perl utility, then the
		top-level makefile will build, test, and install the
		UDUNITS extension module.

Alternatively, you can give `configure' initial values by modifying the file
CUSTOMIZE.

If you need to do unusual things to compile the package, we encourage
you to figure out how `configure' could check whether to do them, and
mail diffs or instructions to the address given in the README so we
can include them in the next release.

2.  Type `make' to compile the package.  If you want, you can override
the `make' variable CFLAGS like this:

	make CFLAGS=-O2

3.  Type `make test' to test the package.

4.  Type `make install' to install programs, data files, and
documentation.  You might need to be the superuser in order to install
the UDUNITS extension utility because the makefile modifies the
installed perl package.

5.  You can remove the program binaries and object files from the
source directory by typing `make clean'.  To also remove the
Makefile(s), the header file containing system-dependent definitions
(if the package uses one), and `config.status' (all the files that
`configure' created), type `make distclean'.

The file `configure.in' is used as a template to create `configure' by
a program called `autoconf'.  You will only need it if you want to
regenerate `configure' using a newer version of `autoconf'.
