   This is a generic INSTALL file for utilities distributions.
If this package does not come with, e.g., installable documentation or
data files, please ignore the references to them below.

   The `configure.com' command procedure attempts to guess correct
values for various system-dependent variables used during compilation,
and creates description file(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.
For those who don't have MMS, or the free clone MMK, configure will
also create necessary command procedures with which you compile, link
and so on.

To compile this package:

1.  Configure the package for your system.

   Normally, you just `set default' to the directory containing the
package's source code and type `@configure'.

   Running `configure.com' takes awhile.  While it is running, it
prints some messages that tell what it is doing.  If you don't want to
see the messages, do `@configure --quiet' instead.

   To compile the package in a different directory from the one
containing the source code, `set default' to the directory where you
want the object files and executables to go and `@SRCDEV:[SRCDIR]configure',
where SRCDEV and SRCDIR are the device and the directory that contains
the source code.  `configure.com' automatically checks for the source
code in the directory that `configure.com' is in and in `[-]'.  If
for some reason `configure.com' is not in the source code directory
that you are configuring, then it will report that it can't find the
source code.  In that case, run `configure.com' with the option
`--srcdir=SRCDEV:[SRCDIR]'.

   By default, `mms install' will install the package's files in
`sys$sysdevice:[gnu.bin]', `sys$sysdevice:[gnu.help]', etc.  You
can specify an installation prefix other than `sys$sysdevice:[gnu]'
by giving `configure.com' the option `--prefix=PATH'.  Alternately,
you can do so by consistently giving a value for the `prefix' variables
when you run `mms', e.g.,
     mms/macro=("prefix_dev"="public:","prefix_dir"="gnu",-
		"prefix"="public:[gnu]")
     mms/macro=("prefix_dev"="public:","prefix_dir"="gnu",-
		"prefix"="public:[gnu]") install

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure.com' the option `--exec-prefix=PATH' or set the `mms'
variables `exec_prefix_dev', `exec_prefix_dir' and `exec_prefix' to the
device part, the directory part (without brackets) of PATH and to PATH
respectivelly, 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 same
prefix.

   Some packages pay attention to `--with-PACKAGE' options to
`configure.com', where PACKAGE is something like `gnu-as' or `x' (for
the X Window System).  They may also pay attention to `--enable-FEATURE'
options, where FEATURE indicates an optional part of the package.  The
README should mention any `--with-' and `--enable-' options that the
package recognizes.

   `configure' also recognizes the following options:
  
`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
     Do not print messages saying which checks are being made.

`--verbose'
     Print the results of the checks.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`--x-includes=DIR'
     X include files are in DIR.

`--x-libraries=DIR'
     X library files are in DIR.

   `configure' also accepts and ignores some other options.

[
  NOTE: This part DOES NOT WORK YET!
     On systems that require unusual options for compilation or linking
  that the package's `configure.com' script does not know about, you can
  give `configure.com' initial values for variables by setting them in
  DCL.  For example:

     $ CC="gcc/standard=portable"
     $ LIBS="public:[libs]weird.olb/lib"
     $ @configure

     Here are the `mms' variables that you might want to override with
  DCL variables when running `configure.com'.

     For these variables, any value given in DCL overrides the value
  that `configure.com' would choose:

   - Variable: CC
       C compiler program.  The default is `cc'.

   - Variable: INSTALL
       Program to use to install files.  The default
       `copy/prot=(s:rwed,o:rwed,g:re,w:re)'

     For these variables, any value given in DCL is added to the value
  that `configure' chooses:

   - Variable: DEFS
       Configuration options, in the form `"foo","bar",...'.  Do not use
       this variable in packages that create a configuration header file.
       The value of this variable will be used when compiling, so the
       above value would result in something like this:

          $ cc/define=("foo","bar",...)

   - Variable: LIBS
       Libraries to link with, in the form
       `dev:[dir]lib1/lib dev:[dir]lib2_shr/share ...'.  The value of this
       variable will eventually end up in an option file, which is used
       during linking.
]

   If you need to do unusual things to compile the package, we encourage
you to figure out how `configure.com' 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 `mms/ignore=warning' to compile the package.  If you want,
you can override the `mms' variables CFLAGS and LDFLAGS like this:

	mms/ignore=warning /macro=(CFLAGS="/DEBUG/NOOPTIMIZE",-
		LDFLAGS="/DEBUG")

3.  If the package comes with self-tests and you want to run them,
type `mms/ignore=warning check'.  If you're not sure whether there are
any, try it; if `mms' responds with something like
    %MMS-F-GWKNOPRN, There are no known sources for the current target CHECK.
then the package does not come with self-tests.

4.  Type `mms/ignore=warning install' to install programs, data files,
and documentation.

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

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