Warning, /education/kard/INSTALL is written in an unsupported language. File is not indexed.

0001 Basic Installation
0002 ==================
0003 
0004    These are generic installation instructions.
0005 
0006    The `configure' shell script attempts to guess correct values for
0007 various system-dependent variables used during compilation.  It uses
0008 those values to create a `Makefile' in each directory of the package.
0009 It may also create one or more `.h' files containing system-dependent
0010 definitions.  Finally, it creates a shell script `config.status' that
0011 you can run in the future to recreate the current configuration, a file
0012 `config.cache' that saves the results of its tests to speed up
0013 reconfiguring, and a file `config.log' containing compiler output
0014 (useful mainly for debugging `configure').
0015 
0016    If you need to do unusual things to compile the package, please try
0017 to figure out how `configure' could check whether to do them, and mail
0018 diffs or instructions to the address given in the `README' so they can
0019 be considered for the next release.  If at some point `config.cache'
0020 contains results you don't want to keep, you may remove or edit it.
0021 
0022    The file `configure.in' is used to create `configure' by a program
0023 called `autoconf'.  You only need `configure.in' if you want to change
0024 it or regenerate `configure' using a newer version of `autoconf'.
0025 
0026 The simplest way to compile this package is:
0027 
0028   1. `cd' to the directory containing the package's source code and type
0029      `./configure' to configure the package for your system.  If you're
0030      using `csh' on an old version of System V, you might need to type
0031      `sh ./configure' instead to prevent `csh' from trying to execute
0032      `configure' itself.
0033 
0034      Running `configure' takes a while.  While running, it prints some
0035      messages telling which features it is checking for.
0036 
0037   2. Type `make' to compile the package.
0038 
0039   3. Type `make install' to install the programs and any data files and
0040      documentation.
0041 
0042   4. You can remove the program binaries and object files from the
0043      source code directory by typing `make clean'.
0044 
0045 Compilers and Options
0046 =====================
0047 
0048    Some systems require unusual options for compilation or linking that
0049 the `configure' script does not know about.  You can give `configure'
0050 initial values for variables by setting them in the environment.  Using
0051 a Bourne-compatible shell, you can do that on the command line like
0052 this:
0053      CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
0054 
0055 Or on systems that have the `env' program, you can do it like this:
0056      env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
0057 
0058 Compiling For Multiple Architectures
0059 ====================================
0060 
0061    You can compile the package for more than one kind of computer at the
0062 same time, by placing the object files for each architecture in their
0063 own directory.  To do this, you must use a version of `make' that
0064 supports the `VPATH' variable, such as GNU `make'.  `cd' to the
0065 directory where you want the object files and executables to go and run
0066 the `configure' script.  `configure' automatically checks for the
0067 source code in the directory that `configure' is in and in `..'.
0068 
0069    If you have to use a `make' that does not supports the `VPATH'
0070 variable, you have to compile the package for one architecture at a time
0071 in the source code directory.  After you have installed the package for
0072 one architecture, use `make distclean' before reconfiguring for another
0073 architecture.
0074 
0075 Installation Names
0076 ==================
0077 
0078    By default, `make install' will install the package's files in
0079 `/usr/local/bin', `/usr/local/man', etc.  You can specify an
0080 installation prefix other than `/usr/local' by giving `configure' the
0081 option `--prefix=PATH'.
0082 
0083    You can specify separate installation prefixes for
0084 architecture-specific files and architecture-independent files.  If you
0085 give `configure' the option `--exec-prefix=PATH', the package will use
0086 PATH as the prefix for installing programs and libraries.
0087 Documentation and other data files will still use the regular prefix.
0088 
0089    If the package supports it, you can cause programs to be installed
0090 with an extra prefix or suffix on their names by giving `configure' the
0091 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
0092 
0093 Optional Features
0094 =================
0095 
0096    Some packages pay attention to `--enable-FEATURE' options to
0097 `configure', where FEATURE indicates an optional part of the package.
0098 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
0099 is something like `gnu-as' or `x' (for the X Window System).  The
0100 `README' should mention any `--enable-' and `--with-' options that the
0101 package recognizes.
0102 
0103    For packages that use the X Window System, `configure' can usually
0104 find the X include and library files automatically, but if it doesn't,
0105 you can use the `configure' options `--x-includes=DIR' and
0106 `--x-libraries=DIR' to specify their locations.
0107 
0108 Specifying the System Type
0109 ==========================
0110 
0111    There may be some features `configure' can not figure out
0112 automatically, but needs to determine by the type of host the package
0113 will run on.  Usually `configure' can figure that out, but if it prints
0114 a message saying it can not guess the host type, give it the
0115 `--host=TYPE' option.  TYPE can either be a short name for the system
0116 type, such as `sun4', or a canonical name with three fields:
0117      CPU-COMPANY-SYSTEM
0118 
0119 See the file `config.sub' for the possible values of each field.  If
0120 `config.sub' isn't included in this package, then this package doesn't
0121 need to know the host type.
0122 
0123    If you are building compiler tools for cross-compiling, you can also
0124 use the `--target=TYPE' option to select the type of system they will
0125 produce code for and the `--build=TYPE' option to select the type of
0126 system on which you are compiling the package.
0127 
0128 Sharing Defaults
0129 ================
0130 
0131    If you want to set default values for `configure' scripts to share,
0132 you can create a site shell script called `config.site' that gives
0133 default values for variables like `CC', `cache_file', and `prefix'.
0134 `configure' looks for `PREFIX/share/config.site' if it exists, then
0135 `PREFIX/etc/config.site' if it exists.  Or, you can set the
0136 `CONFIG_SITE' environment variable to the location of the site script.
0137 A warning: not all `configure' scripts look for a site script.
0138 
0139 Operation Controls
0140 ==================
0141 
0142    `configure' recognizes the following options to control how it
0143 operates.
0144 
0145 `--cache-file=FILE'
0146      Use and save the results of the tests in FILE instead of
0147      `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
0148      debugging `configure'.
0149 
0150 `--help'
0151      Print a summary of the options to `configure', and exit.
0152 
0153 `--quiet'
0154 `--silent'
0155 `-q'
0156      Do not print messages saying which checks are being made.
0157 
0158 `--srcdir=DIR'
0159      Look for the package's source code in directory DIR.  Usually
0160      `configure' can determine that directory automatically.
0161 
0162 `--version'
0163      Print the version of Autoconf used to generate the `configure'
0164      script, and exit.
0165 
0166 `configure' also accepts some other, not widely useful, options.
0167