"Fossies" - the Fresh Open Source Software Archive

Member "abinit-8.10.3/doc/build/using-configure.txt" (24 Jun 2019, 9543 Bytes) of package /linux/misc/abinit-8.10.3.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 Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation, Inc.
    2 Copyright (C) 2004-2018 ABINIT Group
    3 
    4    This file is free documentation; the Free Software Foundation gives
    5 unlimited permission to copy, distribute and modify it.
    6 
    7 Basic Installation
    8 ==================
    9 
   10    These are generic installation instructions. For additional advice
   11 about this specific package, please see the top-level "INSTALL" file.
   12 
   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, and a
   19 file `config.log' containing compiler output (useful mainly for
   20 debugging `configure').
   21 
   22    It can also use an optional file (typically called `config.cache'
   23 and enabled with `--cache-file=config.cache' or simply `-C') that saves
   24 the results of its tests to speed up reconfiguring.  (Caching is
   25 disabled by default to prevent problems with accidental use of stale
   26 cache files.)
   27 
   28    If you need to do unusual things to compile the package, please try
   29 to figure out how `configure' could check whether to do them, and mail
   30 diffs or instructions to the address given in the `README' so they can
   31 be considered for the next release.  If you are using the cache, and at
   32 some point `config.cache' contains results you don't want to keep, you
   33 may remove or edit it.
   34 
   35    The file `configure.ac' (or `configure.in') is used to create
   36 `configure' by a program called `autoconf'.  You only need
   37 `configure.ac' if you want to change it or regenerate `configure' using
   38 a newer version of `autoconf'.
   39 
   40 The simplest way to compile this package is:
   41 
   42   1. `cd' to the directory containing the package's source code and type
   43      `./configure' to configure the package for your system.  If you're
   44      using `csh' on an old version of System V, you might need to type
   45      `sh ./configure' instead to prevent `csh' from trying to execute
   46      `configure' itself.
   47 
   48      Running `configure' takes awhile.  While running, it prints some
   49      messages telling which features it is checking for.
   50 
   51   2. Type `make' to compile the package.
   52 
   53   3. Optionally, type `make check' to run any self-tests that come with
   54      the package.
   55 
   56   4. Type `make install' to install the programs and any data files and
   57      documentation.
   58 
   59   5. You can remove the program binaries and object files from the
   60      source code directory by typing `make clean'.  To also remove the
   61      files that `configure' created (so you can compile the package for
   62      a different kind of computer), type `make distclean'.  There is
   63      also a `make maintainer-clean' target, but that is intended mainly
   64      for the package's developers.  If you use it, you may have to get
   65      all sorts of other programs in order to regenerate files that came
   66      with the distribution.
   67 
   68 Compilers and Options
   69 =====================
   70 
   71    Some systems require unusual options for compilation or linking that
   72 the `configure' script does not know about.  Run `./configure --help'
   73 for details on some of the pertinent environment variables.
   74 
   75    You can give `configure' initial values for variables by setting
   76 them in the environment.  You can do that on the command line like this:
   77 
   78      ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
   79 
   80    *Note Defining Variables::, for more details.
   81 
   82 Compiling For Multiple Architectures
   83 ====================================
   84 
   85    You can compile the package for more than one kind of computer at the
   86 same time, by placing the object files for each architecture in their
   87 own directory.  To do this, you must use a version of `make' that
   88 supports the `VPATH' variable, such as GNU `make'.  `cd' to the
   89 directory where you want the object files and executables to go and run
   90 the `configure' script.  `configure' automatically checks for the
   91 source code in the directory that `configure' is in and in `..'.
   92 
   93    If you have to use a `make' that does not support the `VPATH'
   94 variable, you have to compile the package for one architecture at a
   95 time in the source code directory.  After you have installed the
   96 package for one architecture, use `make distclean' before reconfiguring
   97 for another architecture.
   98 
   99 Installation Names
  100 ==================
  101 
  102    By default, `make install' will install the package's files in
  103 `/usr/local/bin', `/usr/local/man', etc.  You can specify an
  104 installation prefix other than `/usr/local' by giving `configure' the
  105 option `--prefix=PATH'.
  106 
  107    You can specify separate installation prefixes for
  108 architecture-specific files and architecture-independent files.  If you
  109 give `configure' the option `--exec-prefix=PATH', the package will use
  110 PATH as the prefix for installing programs and libraries.
  111 Documentation and other data files will still use the regular prefix.
  112 
  113    In addition, if you use an unusual directory layout you can give
  114 options like `--bindir=PATH' to specify different values for particular
  115 kinds of files.  Run `configure --help' for a list of the directories
  116 you can set and what kinds of files go in them.
  117 
  118    If the package supports it, you can cause programs to be installed
  119 with an extra prefix or suffix on their names by giving `configure' the
  120 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  121 
  122 Optional Features
  123 =================
  124 
  125    Some packages pay attention to `--enable-FEATURE' options to
  126 `configure', where FEATURE indicates an optional part of the package.
  127 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  128 is something like `gnu-as' or `x' (for the X Window System).  The
  129 `README' should mention any `--enable-' and `--with-' options that the
  130 package recognizes.
  131 
  132    For packages that use the X Window System, `configure' can usually
  133 find the X include and library files automatically, but if it doesn't,
  134 you can use the `configure' options `--x-includes=DIR' and
  135 `--x-libraries=DIR' to specify their locations.
  136 
  137 Specifying the System Type
  138 ==========================
  139 
  140    There may be some features `configure' cannot figure out
  141 automatically, but needs to determine by the type of host the package
  142 will run on.  Usually `configure' can figure that out, but if it prints
  143 a message saying it cannot guess the host type, give it the
  144 `--build=TYPE' option.  TYPE can either be a short name for the system
  145 type, such as `sun4', or a canonical name which has the form:
  146 
  147      CPU-COMPANY-SYSTEM
  148 
  149 where SYSTEM can have one of these forms:
  150 
  151      OS KERNEL-OS
  152 
  153    See the file `config.sub' for the possible values of each field.  If
  154 `config.sub' isn't included in this package, then this package doesn't
  155 need to know the host type.
  156 
  157    If you are _building_ compiler tools for cross-compiling, you should
  158 use the `--target=TYPE' option to select the type of system they will
  159 produce code for.
  160 
  161    If you want to _use_ a cross compiler, that generates code for a
  162 platform different from the build platform, you should specify the host
  163 platform (i.e., that on which the generated programs will eventually be
  164 run) with `--host=TYPE'.  In this case, you should also specify the
  165 build platform with `--build=TYPE', because, in this case, it may not
  166 be possible to guess the build platform (it sometimes involves
  167 compiling and running simple test programs, and this can't be done if
  168 the compiler is a cross compiler).
  169 
  170 Sharing Defaults
  171 ================
  172 
  173    If you want to set default values for `configure' scripts to share,
  174 you can create a site shell script called `config.site' that gives
  175 default values for variables like `CC', `cache_file', and `prefix'.
  176 `configure' looks for `PREFIX/share/config.site' if it exists, then
  177 `PREFIX/etc/config.site' if it exists.  Or, you can set the
  178 `CONFIG_SITE' environment variable to the location of the site script.
  179 A warning: not all `configure' scripts look for a site script.
  180 
  181 Defining Variables
  182 ==================
  183 
  184    Variables not defined in a site shell script can be set in the
  185 environment passed to `configure'.  However, some packages may run
  186 configure again during the build, and the customized values of these
  187 variables may be lost.  In order to avoid this problem, you should set
  188 them in the `configure' command line, using `VAR=value'.  For example:
  189 
  190      ./configure CC=/usr/local2/bin/gcc
  191 
  192 will cause the specified gcc to be used as the C compiler (unless it is
  193 overridden in the site shell script).
  194 
  195 `configure' Invocation
  196 ======================
  197 
  198    `configure' recognizes the following options to control how it
  199 operates.
  200 
  201 `--help'
  202 `-h'
  203      Print a summary of the options to `configure', and exit.
  204 
  205 `--version'
  206 `-V'
  207      Print the version of Autoconf used to generate the `configure'
  208      script, and exit.
  209 
  210 `--cache-file=FILE'
  211      Enable the cache: use and save the results of the tests in FILE,
  212      traditionally `config.cache'.  FILE defaults to `/dev/null' to
  213      disable caching.
  214 
  215 `--config-cache'
  216 `-C'
  217      Alias for `--cache-file=config.cache'.
  218 
  219 `--quiet'
  220 `--silent'
  221 `-q'
  222      Do not print messages saying which checks are being made.  To
  223      suppress all normal output, redirect it to `/dev/null' (any error
  224      messages will still be shown).
  225 
  226 `--srcdir=DIR'
  227      Look for the package's source code in directory DIR.  Usually
  228      `configure' can determine that directory automatically.
  229 
  230 `configure' also accepts some other, not widely useful, options.  Run
  231 `configure --help' for more details.
  232