19888Sandreas@sandberg.pp.seInstallation Instructions 29888Sandreas@sandberg.pp.se************************* 39888Sandreas@sandberg.pp.se 49888Sandreas@sandberg.pp.seCopyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software Foundation, 59888Sandreas@sandberg.pp.seInc. 69888Sandreas@sandberg.pp.se 79888Sandreas@sandberg.pp.se Copying and distribution of this file, with or without modification, 89888Sandreas@sandberg.pp.seare permitted in any medium without royalty provided the copyright 99888Sandreas@sandberg.pp.senotice and this notice are preserved. This file is offered as-is, 109888Sandreas@sandberg.pp.sewithout warranty of any kind. 119888Sandreas@sandberg.pp.se 129888Sandreas@sandberg.pp.seBasic Installation 139888Sandreas@sandberg.pp.se================== 149888Sandreas@sandberg.pp.se 159888Sandreas@sandberg.pp.se Briefly, the shell commands `./configure; make; make install' should 169888Sandreas@sandberg.pp.seconfigure, build, and install this package. The following 179888Sandreas@sandberg.pp.semore-detailed instructions are generic; see the `README' file for 189888Sandreas@sandberg.pp.seinstructions specific to this package. Some packages provide this 199888Sandreas@sandberg.pp.se`INSTALL' file but do not implement all of the features documented 209888Sandreas@sandberg.pp.sebelow. The lack of an optional feature in a given package is not 219888Sandreas@sandberg.pp.senecessarily a bug. More recommendations for GNU packages can be found 229888Sandreas@sandberg.pp.sein *note Makefile Conventions: (standards)Makefile Conventions. 239888Sandreas@sandberg.pp.se 249888Sandreas@sandberg.pp.se The `configure' shell script attempts to guess correct values for 259888Sandreas@sandberg.pp.sevarious system-dependent variables used during compilation. It uses 269888Sandreas@sandberg.pp.sethose values to create a `Makefile' in each directory of the package. 279888Sandreas@sandberg.pp.seIt may also create one or more `.h' files containing system-dependent 289888Sandreas@sandberg.pp.sedefinitions. Finally, it creates a shell script `config.status' that 299888Sandreas@sandberg.pp.seyou can run in the future to recreate the current configuration, and a 309888Sandreas@sandberg.pp.sefile `config.log' containing compiler output (useful mainly for 319888Sandreas@sandberg.pp.sedebugging `configure'). 329888Sandreas@sandberg.pp.se 339888Sandreas@sandberg.pp.se It can also use an optional file (typically called `config.cache' 349888Sandreas@sandberg.pp.seand enabled with `--cache-file=config.cache' or simply `-C') that saves 359888Sandreas@sandberg.pp.sethe results of its tests to speed up reconfiguring. Caching is 369888Sandreas@sandberg.pp.sedisabled by default to prevent problems with accidental use of stale 379888Sandreas@sandberg.pp.secache files. 389888Sandreas@sandberg.pp.se 399888Sandreas@sandberg.pp.se If you need to do unusual things to compile the package, please try 409888Sandreas@sandberg.pp.seto figure out how `configure' could check whether to do them, and mail 419888Sandreas@sandberg.pp.sediffs or instructions to the address given in the `README' so they can 429888Sandreas@sandberg.pp.sebe considered for the next release. If you are using the cache, and at 439888Sandreas@sandberg.pp.sesome point `config.cache' contains results you don't want to keep, you 449888Sandreas@sandberg.pp.semay remove or edit it. 459888Sandreas@sandberg.pp.se 469888Sandreas@sandberg.pp.se The file `configure.ac' (or `configure.in') is used to create 479888Sandreas@sandberg.pp.se`configure' by a program called `autoconf'. You need `configure.ac' if 489888Sandreas@sandberg.pp.seyou want to change it or regenerate `configure' using a newer version 499888Sandreas@sandberg.pp.seof `autoconf'. 509888Sandreas@sandberg.pp.se 519888Sandreas@sandberg.pp.se The simplest way to compile this package is: 529888Sandreas@sandberg.pp.se 539888Sandreas@sandberg.pp.se 1. `cd' to the directory containing the package's source code and type 549888Sandreas@sandberg.pp.se `./configure' to configure the package for your system. 559888Sandreas@sandberg.pp.se 569888Sandreas@sandberg.pp.se Running `configure' might take a while. While running, it prints 579888Sandreas@sandberg.pp.se some messages telling which features it is checking for. 589888Sandreas@sandberg.pp.se 599888Sandreas@sandberg.pp.se 2. Type `make' to compile the package. 609888Sandreas@sandberg.pp.se 619888Sandreas@sandberg.pp.se 3. Optionally, type `make check' to run any self-tests that come with 629888Sandreas@sandberg.pp.se the package, generally using the just-built uninstalled binaries. 639888Sandreas@sandberg.pp.se 649888Sandreas@sandberg.pp.se 4. Type `make install' to install the programs and any data files and 659888Sandreas@sandberg.pp.se documentation. When installing into a prefix owned by root, it is 669888Sandreas@sandberg.pp.se recommended that the package be configured and built as a regular 679888Sandreas@sandberg.pp.se user, and only the `make install' phase executed with root 689888Sandreas@sandberg.pp.se privileges. 699888Sandreas@sandberg.pp.se 709888Sandreas@sandberg.pp.se 5. Optionally, type `make installcheck' to repeat any self-tests, but 719888Sandreas@sandberg.pp.se this time using the binaries in their final installed location. 729888Sandreas@sandberg.pp.se This target does not install anything. Running this target as a 739888Sandreas@sandberg.pp.se regular user, particularly if the prior `make install' required 749888Sandreas@sandberg.pp.se root privileges, verifies that the installation completed 759888Sandreas@sandberg.pp.se correctly. 769888Sandreas@sandberg.pp.se 779888Sandreas@sandberg.pp.se 6. You can remove the program binaries and object files from the 789888Sandreas@sandberg.pp.se source code directory by typing `make clean'. To also remove the 799888Sandreas@sandberg.pp.se files that `configure' created (so you can compile the package for 809888Sandreas@sandberg.pp.se a different kind of computer), type `make distclean'. There is 819888Sandreas@sandberg.pp.se also a `make maintainer-clean' target, but that is intended mainly 829888Sandreas@sandberg.pp.se for the package's developers. If you use it, you may have to get 839888Sandreas@sandberg.pp.se all sorts of other programs in order to regenerate files that came 849888Sandreas@sandberg.pp.se with the distribution. 859888Sandreas@sandberg.pp.se 869888Sandreas@sandberg.pp.se 7. Often, you can also type `make uninstall' to remove the installed 879888Sandreas@sandberg.pp.se files again. In practice, not all packages have tested that 889888Sandreas@sandberg.pp.se uninstallation works correctly, even though it is required by the 899888Sandreas@sandberg.pp.se GNU Coding Standards. 909888Sandreas@sandberg.pp.se 919888Sandreas@sandberg.pp.se 8. Some packages, particularly those that use Automake, provide `make 929888Sandreas@sandberg.pp.se distcheck', which can by used by developers to test that all other 939888Sandreas@sandberg.pp.se targets like `make install' and `make uninstall' work correctly. 949888Sandreas@sandberg.pp.se This target is generally not run by end users. 959888Sandreas@sandberg.pp.se 969888Sandreas@sandberg.pp.seCompilers and Options 979888Sandreas@sandberg.pp.se===================== 989888Sandreas@sandberg.pp.se 999888Sandreas@sandberg.pp.se Some systems require unusual options for compilation or linking that 1009888Sandreas@sandberg.pp.sethe `configure' script does not know about. Run `./configure --help' 1019888Sandreas@sandberg.pp.sefor details on some of the pertinent environment variables. 1029888Sandreas@sandberg.pp.se 1039888Sandreas@sandberg.pp.se You can give `configure' initial values for configuration parameters 1049888Sandreas@sandberg.pp.seby setting variables in the command line or in the environment. Here 1059888Sandreas@sandberg.pp.seis an example: 1069888Sandreas@sandberg.pp.se 1079888Sandreas@sandberg.pp.se ./configure CC=c99 CFLAGS=-g LIBS=-lposix 1089888Sandreas@sandberg.pp.se 1099888Sandreas@sandberg.pp.se *Note Defining Variables::, for more details. 1109888Sandreas@sandberg.pp.se 1119888Sandreas@sandberg.pp.seCompiling For Multiple Architectures 1129888Sandreas@sandberg.pp.se==================================== 1139888Sandreas@sandberg.pp.se 1149888Sandreas@sandberg.pp.se You can compile the package for more than one kind of computer at the 1159888Sandreas@sandberg.pp.sesame time, by placing the object files for each architecture in their 1169888Sandreas@sandberg.pp.seown directory. To do this, you can use GNU `make'. `cd' to the 1179888Sandreas@sandberg.pp.sedirectory where you want the object files and executables to go and run 1189888Sandreas@sandberg.pp.sethe `configure' script. `configure' automatically checks for the 1199888Sandreas@sandberg.pp.sesource code in the directory that `configure' is in and in `..'. This 1209888Sandreas@sandberg.pp.seis known as a "VPATH" build. 1219888Sandreas@sandberg.pp.se 1229888Sandreas@sandberg.pp.se With a non-GNU `make', it is safer to compile the package for one 1239888Sandreas@sandberg.pp.searchitecture at a time in the source code directory. After you have 1249888Sandreas@sandberg.pp.seinstalled the package for one architecture, use `make distclean' before 1259888Sandreas@sandberg.pp.sereconfiguring for another architecture. 1269888Sandreas@sandberg.pp.se 1279888Sandreas@sandberg.pp.se On MacOS X 10.5 and later systems, you can create libraries and 1289888Sandreas@sandberg.pp.seexecutables that work on multiple system types--known as "fat" or 1299888Sandreas@sandberg.pp.se"universal" binaries--by specifying multiple `-arch' options to the 1309888Sandreas@sandberg.pp.secompiler but only a single `-arch' option to the preprocessor. Like 1319888Sandreas@sandberg.pp.sethis: 1329888Sandreas@sandberg.pp.se 1339888Sandreas@sandberg.pp.se ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 1349888Sandreas@sandberg.pp.se CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ 1359888Sandreas@sandberg.pp.se CPP="gcc -E" CXXCPP="g++ -E" 1369888Sandreas@sandberg.pp.se 1379888Sandreas@sandberg.pp.se This is not guaranteed to produce working output in all cases, you 1389888Sandreas@sandberg.pp.semay have to build one architecture at a time and combine the results 1399888Sandreas@sandberg.pp.seusing the `lipo' tool if you have problems. 1409888Sandreas@sandberg.pp.se 1419888Sandreas@sandberg.pp.seInstallation Names 1429888Sandreas@sandberg.pp.se================== 1439888Sandreas@sandberg.pp.se 1449888Sandreas@sandberg.pp.se By default, `make install' installs the package's commands under 1459888Sandreas@sandberg.pp.se`/usr/local/bin', include files under `/usr/local/include', etc. You 1469888Sandreas@sandberg.pp.secan specify an installation prefix other than `/usr/local' by giving 1479888Sandreas@sandberg.pp.se`configure' the option `--prefix=PREFIX', where PREFIX must be an 1489888Sandreas@sandberg.pp.seabsolute file name. 1499888Sandreas@sandberg.pp.se 1509888Sandreas@sandberg.pp.se You can specify separate installation prefixes for 1519888Sandreas@sandberg.pp.searchitecture-specific files and architecture-independent files. If you 1529888Sandreas@sandberg.pp.sepass the option `--exec-prefix=PREFIX' to `configure', the package uses 1539888Sandreas@sandberg.pp.sePREFIX as the prefix for installing programs and libraries. 1549888Sandreas@sandberg.pp.seDocumentation and other data files still use the regular prefix. 1559888Sandreas@sandberg.pp.se 1569888Sandreas@sandberg.pp.se In addition, if you use an unusual directory layout you can give 1579888Sandreas@sandberg.pp.seoptions like `--bindir=DIR' to specify different values for particular 1589888Sandreas@sandberg.pp.sekinds of files. Run `configure --help' for a list of the directories 1599888Sandreas@sandberg.pp.seyou can set and what kinds of files go in them. In general, the 1609888Sandreas@sandberg.pp.sedefault for these options is expressed in terms of `${prefix}', so that 1619888Sandreas@sandberg.pp.sespecifying just `--prefix' will affect all of the other directory 1629888Sandreas@sandberg.pp.sespecifications that were not explicitly provided. 1639888Sandreas@sandberg.pp.se 1649888Sandreas@sandberg.pp.se The most portable way to affect installation locations is to pass the 1659888Sandreas@sandberg.pp.secorrect locations to `configure'; however, many packages provide one or 1669888Sandreas@sandberg.pp.seboth of the following shortcuts of passing variable assignments to the 1679888Sandreas@sandberg.pp.se`make install' command line to change installation locations without 1689888Sandreas@sandberg.pp.sehaving to reconfigure or recompile. 1699888Sandreas@sandberg.pp.se 1709888Sandreas@sandberg.pp.se The first method involves providing an override variable for each 1719888Sandreas@sandberg.pp.seaffected directory. For example, `make install 1729888Sandreas@sandberg.pp.seprefix=/alternate/directory' will choose an alternate location for all 1739888Sandreas@sandberg.pp.sedirectory configuration variables that were expressed in terms of 1749888Sandreas@sandberg.pp.se`${prefix}'. Any directories that were specified during `configure', 1759888Sandreas@sandberg.pp.sebut not in terms of `${prefix}', must each be overridden at install 1769888Sandreas@sandberg.pp.setime for the entire installation to be relocated. The approach of 1779888Sandreas@sandberg.pp.semakefile variable overrides for each directory variable is required by 1789888Sandreas@sandberg.pp.sethe GNU Coding Standards, and ideally causes no recompilation. 1799888Sandreas@sandberg.pp.seHowever, some platforms have known limitations with the semantics of 1809888Sandreas@sandberg.pp.seshared libraries that end up requiring recompilation when using this 1819888Sandreas@sandberg.pp.semethod, particularly noticeable in packages that use GNU Libtool. 1829888Sandreas@sandberg.pp.se 1839888Sandreas@sandberg.pp.se The second method involves providing the `DESTDIR' variable. For 1849888Sandreas@sandberg.pp.seexample, `make install DESTDIR=/alternate/directory' will prepend 1859888Sandreas@sandberg.pp.se`/alternate/directory' before all installation names. The approach of 1869888Sandreas@sandberg.pp.se`DESTDIR' overrides is not required by the GNU Coding Standards, and 1879888Sandreas@sandberg.pp.sedoes not work on platforms that have drive letters. On the other hand, 1889888Sandreas@sandberg.pp.seit does better at avoiding recompilation issues, and works well even 1899888Sandreas@sandberg.pp.sewhen some directory options were not specified in terms of `${prefix}' 1909888Sandreas@sandberg.pp.seat `configure' time. 1919888Sandreas@sandberg.pp.se 1929888Sandreas@sandberg.pp.seOptional Features 1939888Sandreas@sandberg.pp.se================= 1949888Sandreas@sandberg.pp.se 1959888Sandreas@sandberg.pp.se If the package supports it, you can cause programs to be installed 1969888Sandreas@sandberg.pp.sewith an extra prefix or suffix on their names by giving `configure' the 1979888Sandreas@sandberg.pp.seoption `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 1989888Sandreas@sandberg.pp.se 1999888Sandreas@sandberg.pp.se Some packages pay attention to `--enable-FEATURE' options to 2009888Sandreas@sandberg.pp.se`configure', where FEATURE indicates an optional part of the package. 2019888Sandreas@sandberg.pp.seThey may also pay attention to `--with-PACKAGE' options, where PACKAGE 2029888Sandreas@sandberg.pp.seis something like `gnu-as' or `x' (for the X Window System). The 2039888Sandreas@sandberg.pp.se`README' should mention any `--enable-' and `--with-' options that the 2049888Sandreas@sandberg.pp.sepackage recognizes. 2059888Sandreas@sandberg.pp.se 2069888Sandreas@sandberg.pp.se For packages that use the X Window System, `configure' can usually 2079888Sandreas@sandberg.pp.sefind the X include and library files automatically, but if it doesn't, 2089888Sandreas@sandberg.pp.seyou can use the `configure' options `--x-includes=DIR' and 2099888Sandreas@sandberg.pp.se`--x-libraries=DIR' to specify their locations. 2109888Sandreas@sandberg.pp.se 2119888Sandreas@sandberg.pp.se Some packages offer the ability to configure how verbose the 2129888Sandreas@sandberg.pp.seexecution of `make' will be. For these packages, running `./configure 2139888Sandreas@sandberg.pp.se--enable-silent-rules' sets the default to minimal output, which can be 2149888Sandreas@sandberg.pp.seoverridden with `make V=1'; while running `./configure 2159888Sandreas@sandberg.pp.se--disable-silent-rules' sets the default to verbose, which can be 2169888Sandreas@sandberg.pp.seoverridden with `make V=0'. 2179888Sandreas@sandberg.pp.se 2189888Sandreas@sandberg.pp.seParticular systems 2199888Sandreas@sandberg.pp.se================== 2209888Sandreas@sandberg.pp.se 2219888Sandreas@sandberg.pp.se On HP-UX, the default C compiler is not ANSI C compatible. If GNU 2229888Sandreas@sandberg.pp.seCC is not installed, it is recommended to use the following options in 2239888Sandreas@sandberg.pp.seorder to use an ANSI C compiler: 2249888Sandreas@sandberg.pp.se 2259888Sandreas@sandberg.pp.se ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" 2269888Sandreas@sandberg.pp.se 2279888Sandreas@sandberg.pp.seand if that doesn't work, install pre-built binaries of GCC for HP-UX. 2289888Sandreas@sandberg.pp.se 2299888Sandreas@sandberg.pp.se HP-UX `make' updates targets which have the same time stamps as 2309888Sandreas@sandberg.pp.setheir prerequisites, which makes it generally unusable when shipped 2319888Sandreas@sandberg.pp.segenerated files such as `configure' are involved. Use GNU `make' 2329888Sandreas@sandberg.pp.seinstead. 2339888Sandreas@sandberg.pp.se 2349888Sandreas@sandberg.pp.se On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot 2359888Sandreas@sandberg.pp.separse its `<wchar.h>' header file. The option `-nodtk' can be used as 2369888Sandreas@sandberg.pp.sea workaround. If GNU CC is not installed, it is therefore recommended 2379888Sandreas@sandberg.pp.seto try 2389888Sandreas@sandberg.pp.se 2399888Sandreas@sandberg.pp.se ./configure CC="cc" 2409888Sandreas@sandberg.pp.se 2419888Sandreas@sandberg.pp.seand if that doesn't work, try 2429888Sandreas@sandberg.pp.se 2439888Sandreas@sandberg.pp.se ./configure CC="cc -nodtk" 2449888Sandreas@sandberg.pp.se 2459888Sandreas@sandberg.pp.se On Solaris, don't put `/usr/ucb' early in your `PATH'. This 2469888Sandreas@sandberg.pp.sedirectory contains several dysfunctional programs; working variants of 2479888Sandreas@sandberg.pp.sethese programs are available in `/usr/bin'. So, if you need `/usr/ucb' 2489888Sandreas@sandberg.pp.sein your `PATH', put it _after_ `/usr/bin'. 2499888Sandreas@sandberg.pp.se 2509888Sandreas@sandberg.pp.se On Haiku, software installed for all users goes in `/boot/common', 2519888Sandreas@sandberg.pp.senot `/usr/local'. It is recommended to use the following options: 2529888Sandreas@sandberg.pp.se 2539888Sandreas@sandberg.pp.se ./configure --prefix=/boot/common 2549888Sandreas@sandberg.pp.se 2559888Sandreas@sandberg.pp.seSpecifying the System Type 2569888Sandreas@sandberg.pp.se========================== 2579888Sandreas@sandberg.pp.se 2589888Sandreas@sandberg.pp.se There may be some features `configure' cannot figure out 2599888Sandreas@sandberg.pp.seautomatically, but needs to determine by the type of machine the package 2609888Sandreas@sandberg.pp.sewill run on. Usually, assuming the package is built to be run on the 2619888Sandreas@sandberg.pp.se_same_ architectures, `configure' can figure that out, but if it prints 2629888Sandreas@sandberg.pp.sea message saying it cannot guess the machine type, give it the 2639888Sandreas@sandberg.pp.se`--build=TYPE' option. TYPE can either be a short name for the system 2649888Sandreas@sandberg.pp.setype, such as `sun4', or a canonical name which has the form: 2659888Sandreas@sandberg.pp.se 2669888Sandreas@sandberg.pp.se CPU-COMPANY-SYSTEM 2679888Sandreas@sandberg.pp.se 2689888Sandreas@sandberg.pp.sewhere SYSTEM can have one of these forms: 2699888Sandreas@sandberg.pp.se 2709888Sandreas@sandberg.pp.se OS 2719888Sandreas@sandberg.pp.se KERNEL-OS 2729888Sandreas@sandberg.pp.se 2739888Sandreas@sandberg.pp.se See the file `config.sub' for the possible values of each field. If 2749888Sandreas@sandberg.pp.se`config.sub' isn't included in this package, then this package doesn't 2759888Sandreas@sandberg.pp.seneed to know the machine type. 2769888Sandreas@sandberg.pp.se 2779888Sandreas@sandberg.pp.se If you are _building_ compiler tools for cross-compiling, you should 2789888Sandreas@sandberg.pp.seuse the option `--target=TYPE' to select the type of system they will 2799888Sandreas@sandberg.pp.seproduce code for. 2809888Sandreas@sandberg.pp.se 2819888Sandreas@sandberg.pp.se If you want to _use_ a cross compiler, that generates code for a 2829888Sandreas@sandberg.pp.seplatform different from the build platform, you should specify the 2839888Sandreas@sandberg.pp.se"host" platform (i.e., that on which the generated programs will 2849888Sandreas@sandberg.pp.seeventually be run) with `--host=TYPE'. 2859888Sandreas@sandberg.pp.se 2869888Sandreas@sandberg.pp.seSharing Defaults 2879888Sandreas@sandberg.pp.se================ 2889888Sandreas@sandberg.pp.se 2899888Sandreas@sandberg.pp.se If you want to set default values for `configure' scripts to share, 2909888Sandreas@sandberg.pp.seyou can create a site shell script called `config.site' that gives 2919888Sandreas@sandberg.pp.sedefault values for variables like `CC', `cache_file', and `prefix'. 2929888Sandreas@sandberg.pp.se`configure' looks for `PREFIX/share/config.site' if it exists, then 2939888Sandreas@sandberg.pp.se`PREFIX/etc/config.site' if it exists. Or, you can set the 2949888Sandreas@sandberg.pp.se`CONFIG_SITE' environment variable to the location of the site script. 2959888Sandreas@sandberg.pp.seA warning: not all `configure' scripts look for a site script. 2969888Sandreas@sandberg.pp.se 2979888Sandreas@sandberg.pp.seDefining Variables 2989888Sandreas@sandberg.pp.se================== 2999888Sandreas@sandberg.pp.se 3009888Sandreas@sandberg.pp.se Variables not defined in a site shell script can be set in the 3019888Sandreas@sandberg.pp.seenvironment passed to `configure'. However, some packages may run 3029888Sandreas@sandberg.pp.seconfigure again during the build, and the customized values of these 3039888Sandreas@sandberg.pp.sevariables may be lost. In order to avoid this problem, you should set 3049888Sandreas@sandberg.pp.sethem in the `configure' command line, using `VAR=value'. For example: 3059888Sandreas@sandberg.pp.se 3069888Sandreas@sandberg.pp.se ./configure CC=/usr/local2/bin/gcc 3079888Sandreas@sandberg.pp.se 3089888Sandreas@sandberg.pp.secauses the specified `gcc' to be used as the C compiler (unless it is 3099888Sandreas@sandberg.pp.seoverridden in the site shell script). 3109888Sandreas@sandberg.pp.se 3119888Sandreas@sandberg.pp.seUnfortunately, this technique does not work for `CONFIG_SHELL' due to 3129888Sandreas@sandberg.pp.sean Autoconf bug. Until the bug is fixed you can use this workaround: 3139888Sandreas@sandberg.pp.se 3149888Sandreas@sandberg.pp.se CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash 3159888Sandreas@sandberg.pp.se 3169888Sandreas@sandberg.pp.se`configure' Invocation 3179888Sandreas@sandberg.pp.se====================== 3189888Sandreas@sandberg.pp.se 3199888Sandreas@sandberg.pp.se `configure' recognizes the following options to control how it 3209888Sandreas@sandberg.pp.seoperates. 3219888Sandreas@sandberg.pp.se 3229888Sandreas@sandberg.pp.se`--help' 3239888Sandreas@sandberg.pp.se`-h' 3249888Sandreas@sandberg.pp.se Print a summary of all of the options to `configure', and exit. 3259888Sandreas@sandberg.pp.se 3269888Sandreas@sandberg.pp.se`--help=short' 3279888Sandreas@sandberg.pp.se`--help=recursive' 3289888Sandreas@sandberg.pp.se Print a summary of the options unique to this package's 3299888Sandreas@sandberg.pp.se `configure', and exit. The `short' variant lists options used 3309888Sandreas@sandberg.pp.se only in the top level, while the `recursive' variant lists options 3319888Sandreas@sandberg.pp.se also present in any nested packages. 3329888Sandreas@sandberg.pp.se 3339888Sandreas@sandberg.pp.se`--version' 3349888Sandreas@sandberg.pp.se`-V' 3359888Sandreas@sandberg.pp.se Print the version of Autoconf used to generate the `configure' 3369888Sandreas@sandberg.pp.se script, and exit. 3379888Sandreas@sandberg.pp.se 3389888Sandreas@sandberg.pp.se`--cache-file=FILE' 3399888Sandreas@sandberg.pp.se Enable the cache: use and save the results of the tests in FILE, 3409888Sandreas@sandberg.pp.se traditionally `config.cache'. FILE defaults to `/dev/null' to 3419888Sandreas@sandberg.pp.se disable caching. 3429888Sandreas@sandberg.pp.se 3439888Sandreas@sandberg.pp.se`--config-cache' 3449888Sandreas@sandberg.pp.se`-C' 3459888Sandreas@sandberg.pp.se Alias for `--cache-file=config.cache'. 3469888Sandreas@sandberg.pp.se 3479888Sandreas@sandberg.pp.se`--quiet' 3489888Sandreas@sandberg.pp.se`--silent' 3499888Sandreas@sandberg.pp.se`-q' 3509888Sandreas@sandberg.pp.se Do not print messages saying which checks are being made. To 3519888Sandreas@sandberg.pp.se suppress all normal output, redirect it to `/dev/null' (any error 3529888Sandreas@sandberg.pp.se messages will still be shown). 3539888Sandreas@sandberg.pp.se 3549888Sandreas@sandberg.pp.se`--srcdir=DIR' 3559888Sandreas@sandberg.pp.se Look for the package's source code in directory DIR. Usually 3569888Sandreas@sandberg.pp.se `configure' can determine that directory automatically. 3579888Sandreas@sandberg.pp.se 3589888Sandreas@sandberg.pp.se`--prefix=DIR' 3599888Sandreas@sandberg.pp.se Use DIR as the installation prefix. *note Installation Names:: 3609888Sandreas@sandberg.pp.se for more details, including other options available for fine-tuning 3619888Sandreas@sandberg.pp.se the installation locations. 3629888Sandreas@sandberg.pp.se 3639888Sandreas@sandberg.pp.se`--no-create' 3649888Sandreas@sandberg.pp.se`-n' 3659888Sandreas@sandberg.pp.se Run the configure checks, but stop before creating any output 3669888Sandreas@sandberg.pp.se files. 3679888Sandreas@sandberg.pp.se 3689888Sandreas@sandberg.pp.se`configure' also accepts some other, not widely useful, options. Run 3699888Sandreas@sandberg.pp.se`configure --help' for more details. 3709888Sandreas@sandberg.pp.se 371