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