"Fossies" - the Fresh Open Source Software Archive

Member "amavisd-milter-1.7.2/INSTALL" (6 Jan 2019, 6833 Bytes) of package /linux/privat/amavisd-milter-1.7.2.tar.gz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Obtaining the software
    2 ======================
    4 Fetch the tarball from GitHub and unpack it:
    6   https://github.com/prehor/amavisd-milter/releases
    8 Start reading with README.md, then CHANGES and INSTALL.
   10 Basic Installation
   11 ==================
   13 The `configure' shell script attempts to guess correct values for
   14 various system-dependent variables used during compilation.  It uses
   15 those values to create a `Makefile' in each directory of the package.
   16 It may also create one or more `.h' files containing system-dependent
   17 definitions.  Finally, it creates a shell script `config.status' that
   18 you can run in the future to recreate the current configuration, a file
   19 `config.cache' that saves the results of its tests to speed up
   20 reconfiguring, and a file `config.log' containing compiler output
   21 (useful mainly for debugging `configure').
   23 If you need to do unusual things to compile the package, please try
   24 to figure out how `configure' could check whether to do them, and mail
   25 diffs or instructions to the address given in the `README' so they can
   26 be considered for the next release.  If at some point `config.cache'
   27 contains results you don't want to keep, you may remove or edit it.
   29 The file `configure.in' is used to create `configure' by a program
   30 called `autoconf'.  You only need `configure.in' if you want to change
   31 it or regenerate `configure' using a newer version of `autoconf'.
   33 The simplest way to compile this package is:
   35   1. `cd' to the directory containing the package's source code and type
   36      `./configure' to configure the package for your system.  If you're
   37      using `csh' on an old version of System V, you might need to type
   38      `sh ./configure' instead to prevent `csh' from trying to execute
   39      `configure' itself.
   41      Running `configure' takes a while.  While running, it prints some
   42      messages telling which features it is checking for.
   44   2. Type `make' to compile the package.
   46   3. Type `make install' to install the programs and any data files and
   47      documentation.
   49   4. You can remove the program binaries and object files from the
   50      source code directory by typing `make clean'.
   52 Compilers and Options
   53 =====================
   55 Some systems require unusual options for compilation or linking that
   56 the `configure' script does not know about.  You can give `configure'
   57 initial values for variables by setting them in the environment.  Using
   58 a Bourne-compatible shell, you can do that on the command line like
   59 this:
   61      CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
   63 Or on systems that have the `env' program, you can do it like this:
   65      env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
   67 Compiling For Multiple Architectures
   68 ====================================
   70 You can compile the package for more than one kind of computer at the
   71 same time, by placing the object files for each architecture in their
   72 own directory.  To do this, you must use a version of `make' that
   73 supports the `VPATH' variable, such as GNU `make'.  `cd' to the
   74 directory where you want the object files and executables to go and run
   75 the `configure' script.  `configure' automatically checks for the
   76 source code in the directory that `configure' is in and in `..'.
   78 If you have to use a `make' that does not supports the `VPATH'
   79 variable, you have to compile the package for one architecture at a time
   80 in the source code directory.  After you have installed the package for
   81 one architecture, use `make distclean' before reconfiguring for another
   82 architecture.
   84 Installation Names
   85 ==================
   87 By default, `make install' will install the package's files in
   88 `/usr/local/bin', `/usr/local/man', etc.  You can specify an
   89 installation prefix other than `/usr/local' by giving `configure' the
   90 option `--prefix=PATH'.
   92 You can specify separate installation prefixes for
   93 architecture-specific files and architecture-independent files.  If you
   94 give `configure' the option `--exec-prefix=PATH', the package will use
   95 PATH as the prefix for installing programs and libraries.
   96 Documentation and other data files will still use the regular prefix.
   98 If the package supports it, you can cause programs to be installed
   99 with an extra prefix or suffix on their names by giving `configure' the
  100 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  102 Optional Features
  103 =================
  105 Some packages pay attention to `--enable-FEATURE' options to
  106 `configure', where FEATURE indicates an optional part of the package.
  107 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  108 is something like `gnu-as' or `x' (for the X Window System).  The
  109 `README' should mention any `--enable-' and `--with-' options that the
  110 package recognizes.
  112 Specifying the System Type
  113 ==========================
  115 There may be some features `configure' can not figure out
  116 automatically, but needs to determine by the type of host the package
  117 will run on.  Usually `configure' can figure that out, but if it prints
  118 a message saying it can not guess the host type, give it the
  119 `--host=TYPE' option.  TYPE can either be a short name for the system
  120 type, such as `sun4', or a canonical name with three fields:
  124 See the file `config.sub' for the possible values of each field.  If
  125 `config.sub' isn't included in this package, then this package doesn't
  126 need to know the host type.
  128 If you are building compiler tools for cross-compiling, you can also
  129 use the `--target=TYPE' option to select the type of system they will
  130 produce code for and the `--build=TYPE' option to select the type of
  131 system on which you are compiling the package.
  133 Sharing Defaults
  134 ================
  136 If you want to set default values for `configure' scripts to share,
  137 you can create a site shell script called `config.site' that gives
  138 default values for variables like `CC', `cache_file', and `prefix'.
  139 `configure' looks for `PREFIX/share/config.site' if it exists, then
  140 `PREFIX/etc/config.site' if it exists.  Or, you can set the
  141 `CONFIG_SITE' environment variable to the location of the site script.
  142 A warning: not all `configure' scripts look for a site script.
  144 Operation Controls
  145 ==================
  147 `configure' recognizes the following options to control how it
  148 operates.
  150 `--cache-file=FILE'
  151      Use and save the results of the tests in FILE instead of
  152      `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
  153      debugging `configure'.
  155 `--help'
  156      Print a summary of the options to `configure', and exit.
  158 `--quiet'
  159 `--silent'
  160 `-q'
  161      Do not print messages saying which checks are being made.
  163 `--srcdir=DIR'
  164      Look for the package's source code in directory DIR.  Usually
  165      `configure' can determine that directory automatically.
  167 `--version'
  168      Print the version of Autoconf used to generate the `configure'
  169      script, and exit.
  171 `configure' also accepts some other, not widely useful, options.