nut-debian/INSTALL

369 lines
15 KiB
Plaintext
Raw Normal View History

2014-04-22 21:39:47 +03:00
Installation Instructions
*************************
2022-07-10 10:23:45 +03:00
Copyright (C) 1994-1996, 1999-2002, 2004-2016 Free Software
Foundation, Inc.
2014-04-22 21:39:47 +03:00
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
Basic Installation
==================
2022-07-10 10:23:45 +03:00
Briefly, the shell command './configure && make && make install'
2015-04-30 16:53:36 +03:00
should configure, build, and install this package. The following
2022-07-10 10:23:45 +03:00
more-detailed instructions are generic; see the 'README' file for
2014-04-22 21:39:47 +03:00
instructions specific to this package. Some packages provide this
2022-07-10 10:23:45 +03:00
'INSTALL' file but do not implement all of the features documented
2014-04-22 21:39:47 +03:00
below. The lack of an optional feature in a given package is not
necessarily a bug. More recommendations for GNU packages can be found
in *note Makefile Conventions: (standards)Makefile Conventions.
2022-07-10 10:23:45 +03:00
The 'configure' shell script attempts to guess correct values for
2014-04-22 21:39:47 +03:00
various system-dependent variables used during compilation. It uses
2022-07-10 10:23:45 +03:00
those values to create a 'Makefile' in each directory of the package.
It may also create one or more '.h' files containing system-dependent
definitions. Finally, it creates a shell script 'config.status' that
2014-04-22 21:39:47 +03:00
you can run in the future to recreate the current configuration, and a
2022-07-10 10:23:45 +03:00
file 'config.log' containing compiler output (useful mainly for
debugging 'configure').
2014-04-22 21:39:47 +03:00
2022-07-10 10:23:45 +03:00
It can also use an optional file (typically called 'config.cache' and
enabled with '--cache-file=config.cache' or simply '-C') that saves the
results of its tests to speed up reconfiguring. Caching is disabled by
default to prevent problems with accidental use of stale cache files.
2014-04-22 21:39:47 +03:00
If you need to do unusual things to compile the package, please try
2022-07-10 10:23:45 +03:00
to figure out how 'configure' could check whether to do them, and mail
diffs or instructions to the address given in the 'README' so they can
2014-04-22 21:39:47 +03:00
be considered for the next release. If you are using the cache, and at
2022-07-10 10:23:45 +03:00
some point 'config.cache' contains results you don't want to keep, you
2014-04-22 21:39:47 +03:00
may remove or edit it.
2022-07-10 10:23:45 +03:00
The file 'configure.ac' (or 'configure.in') is used to create
'configure' by a program called 'autoconf'. You need 'configure.ac' if
you want to change it or regenerate 'configure' using a newer version of
'autoconf'.
2014-04-22 21:39:47 +03:00
The simplest way to compile this package is:
2022-07-10 10:23:45 +03:00
1. 'cd' to the directory containing the package's source code and type
'./configure' to configure the package for your system.
2014-04-22 21:39:47 +03:00
2022-07-10 10:23:45 +03:00
Running 'configure' might take a while. While running, it prints
2014-04-22 21:39:47 +03:00
some messages telling which features it is checking for.
2022-07-10 10:23:45 +03:00
2. Type 'make' to compile the package.
2014-04-22 21:39:47 +03:00
2022-07-10 10:23:45 +03:00
3. Optionally, type 'make check' to run any self-tests that come with
2014-04-22 21:39:47 +03:00
the package, generally using the just-built uninstalled binaries.
2022-07-10 10:23:45 +03:00
4. Type 'make install' to install the programs and any data files and
2014-04-22 21:39:47 +03:00
documentation. When installing into a prefix owned by root, it is
recommended that the package be configured and built as a regular
2022-07-10 10:23:45 +03:00
user, and only the 'make install' phase executed with root
2014-04-22 21:39:47 +03:00
privileges.
2022-07-10 10:23:45 +03:00
5. Optionally, type 'make installcheck' to repeat any self-tests, but
2014-04-22 21:39:47 +03:00
this time using the binaries in their final installed location.
This target does not install anything. Running this target as a
2022-07-10 10:23:45 +03:00
regular user, particularly if the prior 'make install' required
2014-04-22 21:39:47 +03:00
root privileges, verifies that the installation completed
correctly.
6. You can remove the program binaries and object files from the
2022-07-10 10:23:45 +03:00
source code directory by typing 'make clean'. To also remove the
files that 'configure' created (so you can compile the package for
a different kind of computer), type 'make distclean'. There is
also a 'make maintainer-clean' target, but that is intended mainly
2014-04-22 21:39:47 +03:00
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
2022-07-10 10:23:45 +03:00
7. Often, you can also type 'make uninstall' to remove the installed
2014-04-22 21:39:47 +03:00
files again. In practice, not all packages have tested that
uninstallation works correctly, even though it is required by the
GNU Coding Standards.
2022-07-10 10:23:45 +03:00
8. Some packages, particularly those that use Automake, provide 'make
2014-04-22 21:39:47 +03:00
distcheck', which can by used by developers to test that all other
2022-07-10 10:23:45 +03:00
targets like 'make install' and 'make uninstall' work correctly.
2014-04-22 21:39:47 +03:00
This target is generally not run by end users.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
2022-07-10 10:23:45 +03:00
the 'configure' script does not know about. Run './configure --help'
2014-04-22 21:39:47 +03:00
for details on some of the pertinent environment variables.
2022-07-10 10:23:45 +03:00
You can give 'configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here is
an example:
2014-04-22 21:39:47 +03:00
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
2022-07-10 10:23:45 +03:00
own directory. To do this, you can use GNU 'make'. 'cd' to the
2014-04-22 21:39:47 +03:00
directory where you want the object files and executables to go and run
2022-07-10 10:23:45 +03:00
the 'configure' script. 'configure' automatically checks for the source
code in the directory that 'configure' is in and in '..'. This is known
as a "VPATH" build.
2014-04-22 21:39:47 +03:00
2022-07-10 10:23:45 +03:00
With a non-GNU 'make', it is safer to compile the package for one
2014-04-22 21:39:47 +03:00
architecture at a time in the source code directory. After you have
2022-07-10 10:23:45 +03:00
installed the package for one architecture, use 'make distclean' before
2014-04-22 21:39:47 +03:00
reconfiguring for another architecture.
On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
2022-07-10 10:23:45 +03:00
"universal" binaries--by specifying multiple '-arch' options to the
compiler but only a single '-arch' option to the preprocessor. Like
2014-04-22 21:39:47 +03:00
this:
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CPP="gcc -E" CXXCPP="g++ -E"
This is not guaranteed to produce working output in all cases, you
may have to build one architecture at a time and combine the results
2022-07-10 10:23:45 +03:00
using the 'lipo' tool if you have problems.
2014-04-22 21:39:47 +03:00
Installation Names
==================
2022-07-10 10:23:45 +03:00
By default, 'make install' installs the package's commands under
'/usr/local/bin', include files under '/usr/local/include', etc. You
can specify an installation prefix other than '/usr/local' by giving
'configure' the option '--prefix=PREFIX', where PREFIX must be an
2014-04-22 21:39:47 +03:00
absolute file name.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
2022-07-10 10:23:45 +03:00
pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
2014-04-22 21:39:47 +03:00
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
2022-07-10 10:23:45 +03:00
options like '--bindir=DIR' to specify different values for particular
kinds of files. Run 'configure --help' for a list of the directories
you can set and what kinds of files go in them. In general, the default
for these options is expressed in terms of '${prefix}', so that
specifying just '--prefix' will affect all of the other directory
2014-04-22 21:39:47 +03:00
specifications that were not explicitly provided.
The most portable way to affect installation locations is to pass the
2022-07-10 10:23:45 +03:00
correct locations to 'configure'; however, many packages provide one or
2014-04-22 21:39:47 +03:00
both of the following shortcuts of passing variable assignments to the
2022-07-10 10:23:45 +03:00
'make install' command line to change installation locations without
2014-04-22 21:39:47 +03:00
having to reconfigure or recompile.
The first method involves providing an override variable for each
2022-07-10 10:23:45 +03:00
affected directory. For example, 'make install
2014-04-22 21:39:47 +03:00
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
2022-07-10 10:23:45 +03:00
'${prefix}'. Any directories that were specified during 'configure',
but not in terms of '${prefix}', must each be overridden at install time
for the entire installation to be relocated. The approach of makefile
variable overrides for each directory variable is required by the GNU
Coding Standards, and ideally causes no recompilation. However, some
platforms have known limitations with the semantics of shared libraries
that end up requiring recompilation when using this method, particularly
noticeable in packages that use GNU Libtool.
The second method involves providing the 'DESTDIR' variable. For
example, 'make install DESTDIR=/alternate/directory' will prepend
'/alternate/directory' before all installation names. The approach of
'DESTDIR' overrides is not required by the GNU Coding Standards, and
2014-04-22 21:39:47 +03:00
does not work on platforms that have drive letters. On the other hand,
it does better at avoiding recompilation issues, and works well even
2022-07-10 10:23:45 +03:00
when some directory options were not specified in terms of '${prefix}'
at 'configure' time.
2014-04-22 21:39:47 +03:00
Optional Features
=================
If the package supports it, you can cause programs to be installed
2022-07-10 10:23:45 +03:00
with an extra prefix or suffix on their names by giving 'configure' the
option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
Some packages pay attention to '--enable-FEATURE' options to
'configure', where FEATURE indicates an optional part of the package.
They may also pay attention to '--with-PACKAGE' options, where PACKAGE
is something like 'gnu-as' or 'x' (for the X Window System). The
'README' should mention any '--enable-' and '--with-' options that the
2014-04-22 21:39:47 +03:00
package recognizes.
2022-07-10 10:23:45 +03:00
For packages that use the X Window System, 'configure' can usually
2014-04-22 21:39:47 +03:00
find the X include and library files automatically, but if it doesn't,
2022-07-10 10:23:45 +03:00
you can use the 'configure' options '--x-includes=DIR' and
'--x-libraries=DIR' to specify their locations.
2014-04-22 21:39:47 +03:00
Some packages offer the ability to configure how verbose the
2022-07-10 10:23:45 +03:00
execution of 'make' will be. For these packages, running './configure
2014-04-22 21:39:47 +03:00
--enable-silent-rules' sets the default to minimal output, which can be
2022-07-10 10:23:45 +03:00
overridden with 'make V=1'; while running './configure
2014-04-22 21:39:47 +03:00
--disable-silent-rules' sets the default to verbose, which can be
2022-07-10 10:23:45 +03:00
overridden with 'make V=0'.
2014-04-22 21:39:47 +03:00
Particular systems
==================
2022-07-10 10:23:45 +03:00
On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
is not installed, it is recommended to use the following options in
2014-04-22 21:39:47 +03:00
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
2022-07-10 10:23:45 +03:00
HP-UX 'make' updates targets which have the same time stamps as their
prerequisites, which makes it generally unusable when shipped generated
files such as 'configure' are involved. Use GNU 'make' instead.
2014-04-22 21:39:47 +03:00
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
2022-07-10 10:23:45 +03:00
parse its '<wchar.h>' header file. The option '-nodtk' can be used as a
workaround. If GNU CC is not installed, it is therefore recommended to
try
2014-04-22 21:39:47 +03:00
./configure CC="cc"
and if that doesn't work, try
./configure CC="cc -nodtk"
2022-07-10 10:23:45 +03:00
On Solaris, don't put '/usr/ucb' early in your 'PATH'. This
2014-04-22 21:39:47 +03:00
directory contains several dysfunctional programs; working variants of
2022-07-10 10:23:45 +03:00
these programs are available in '/usr/bin'. So, if you need '/usr/ucb'
in your 'PATH', put it _after_ '/usr/bin'.
2014-04-22 21:39:47 +03:00
2022-07-10 10:23:45 +03:00
On Haiku, software installed for all users goes in '/boot/common',
not '/usr/local'. It is recommended to use the following options:
2014-04-22 21:39:47 +03:00
./configure --prefix=/boot/common
Specifying the System Type
==========================
2022-07-10 10:23:45 +03:00
There may be some features 'configure' cannot figure out
2014-04-22 21:39:47 +03:00
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
2022-07-10 10:23:45 +03:00
_same_ architectures, 'configure' can figure that out, but if it prints
2014-04-22 21:39:47 +03:00
a message saying it cannot guess the machine type, give it the
2022-07-10 10:23:45 +03:00
'--build=TYPE' option. TYPE can either be a short name for the system
type, such as 'sun4', or a canonical name which has the form:
2014-04-22 21:39:47 +03:00
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS
KERNEL-OS
2022-07-10 10:23:45 +03:00
See the file 'config.sub' for the possible values of each field. If
'config.sub' isn't included in this package, then this package doesn't
2014-04-22 21:39:47 +03:00
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
2022-07-10 10:23:45 +03:00
use the option '--target=TYPE' to select the type of system they will
2014-04-22 21:39:47 +03:00
produce code for.
2010-03-26 01:20:59 +02:00
2014-04-22 21:39:47 +03:00
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
2022-07-10 10:23:45 +03:00
eventually be run) with '--host=TYPE'.
2010-03-26 01:20:59 +02:00
2014-04-22 21:39:47 +03:00
Sharing Defaults
================
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
If you want to set default values for 'configure' scripts to share,
you can create a site shell script called 'config.site' that gives
default values for variables like 'CC', 'cache_file', and 'prefix'.
'configure' looks for 'PREFIX/share/config.site' if it exists, then
'PREFIX/etc/config.site' if it exists. Or, you can set the
'CONFIG_SITE' environment variable to the location of the site script.
A warning: not all 'configure' scripts look for a site script.
2010-03-26 01:20:59 +02:00
2014-04-22 21:39:47 +03:00
Defining Variables
==================
2011-01-26 11:35:08 +02:00
2014-04-22 21:39:47 +03:00
Variables not defined in a site shell script can be set in the
2022-07-10 10:23:45 +03:00
environment passed to 'configure'. However, some packages may run
2014-04-22 21:39:47 +03:00
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
2022-07-10 10:23:45 +03:00
them in the 'configure' command line, using 'VAR=value'. For example:
2011-01-26 11:35:08 +02:00
2014-04-22 21:39:47 +03:00
./configure CC=/usr/local2/bin/gcc
2011-01-26 11:35:08 +02:00
2022-07-10 10:23:45 +03:00
causes the specified 'gcc' to be used as the C compiler (unless it is
2014-04-22 21:39:47 +03:00
overridden in the site shell script).
2011-01-26 11:35:08 +02:00
2022-07-10 10:23:45 +03:00
Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
Autoconf limitation. Until the limitation is lifted, you can use this
workaround:
2010-03-26 01:20:59 +02:00
2015-04-30 16:53:36 +03:00
CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'configure' Invocation
2014-04-22 21:39:47 +03:00
======================
2011-01-26 11:35:08 +02:00
2022-07-10 10:23:45 +03:00
'configure' recognizes the following options to control how it
2014-04-22 21:39:47 +03:00
operates.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--help'
'-h'
Print a summary of all of the options to 'configure', and exit.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--help=short'
'--help=recursive'
2014-04-22 21:39:47 +03:00
Print a summary of the options unique to this package's
2022-07-10 10:23:45 +03:00
'configure', and exit. The 'short' variant lists options used only
in the top level, while the 'recursive' variant lists options also
present in any nested packages.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--version'
'-V'
Print the version of Autoconf used to generate the 'configure'
2014-04-22 21:39:47 +03:00
script, and exit.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--cache-file=FILE'
2014-04-22 21:39:47 +03:00
Enable the cache: use and save the results of the tests in FILE,
2022-07-10 10:23:45 +03:00
traditionally 'config.cache'. FILE defaults to '/dev/null' to
2014-04-22 21:39:47 +03:00
disable caching.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--config-cache'
'-C'
Alias for '--cache-file=config.cache'.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--quiet'
'--silent'
'-q'
2014-04-22 21:39:47 +03:00
Do not print messages saying which checks are being made. To
2022-07-10 10:23:45 +03:00
suppress all normal output, redirect it to '/dev/null' (any error
2014-04-22 21:39:47 +03:00
messages will still be shown).
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--srcdir=DIR'
2014-04-22 21:39:47 +03:00
Look for the package's source code in directory DIR. Usually
2022-07-10 10:23:45 +03:00
'configure' can determine that directory automatically.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--prefix=DIR'
Use DIR as the installation prefix. *note Installation Names:: for
more details, including other options available for fine-tuning the
installation locations.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'--no-create'
'-n'
2014-04-22 21:39:47 +03:00
Run the configure checks, but stop before creating any output
files.
2010-03-26 01:20:59 +02:00
2022-07-10 10:23:45 +03:00
'configure' also accepts some other, not widely useful, options. Run
'configure --help' for more details.