aboutsummaryrefslogblamecommitdiffstats
path: root/INSTALL
blob: b42a17ac4640e9a2bfe5e480e44d0eef3f365928 (plain) (tree)




















































































































































































                                                                        
Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
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
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
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
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     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
     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.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

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
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' 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.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   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
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

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
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   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.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.
lt;osa@FreeBSD.org> 2004-01-29 21:32:12 +0800 Add a new port atmsupport: contains a number of' href='/~lantw44/cgit/cgit.cgi/freebsd-ports-gnome/commit/net/Makefile?id=9ea0175cbb7e837543b5549f1386b28405a13f56'>9ea0175cbb7e
caee31e2dc64
81f633ad3ff2
e6d6b54a027c
c6f054d5567b
e727319eb468
c7c6d3947144
8bbdddec2537
2a1d5794f42c
440e132ce9a1
1c043a044857
91263a63198f
2659f6e82c4a
d9abbbd33e3d
70f251519484
c4a2c0bf2660
bdb20e14fee8
8bc326a6ea30
5960fe7b0bb3
5ced78255685
4db71470d61a
6a9161318fb3
93bea4ceac45
e05a5f3b6653
10ad823b2d60
20a6575a354b
48d67f1f884b
594955596c88
8ebb326aa981
b5792cb6f59c
3cbc90e8ecd3
a3b9cad463c9
8dad386ac037
a3b9cad463c9
9628afde92aa
d14ebf95c153
8db6b7f0850a
0a8955e3e774
0f7131f21826
4739d0f153fe
d2da40c7d944
b88c1c1e5b78
edfb4a9aac73
6eb2f983e8d4
718cbeaa52ed
487e234a3c47
f3f78280558a
2a894ea487d8
60759483695c
c98928ee3d9d
584db33f4365
34c167517c92
a8513e45b046
51e46c2023c8
332e4d9f8ffc
2559658b55c7
2a823c2f37db
8b4a4419cd38
286af87ebfc5
fabc6c829c34
5fb357ef903a
f66784481e6e
6214e3e7eceb
293f3790f753
d9b72f8ebcfe
40684706f879
ce60f3535547
17898aead5d4
3b537ed478b4
f0ce4387e4be
db2d1f435ffa
f9dfcacf7d5d
08fc8d9bbc07
54edabeda9b3
169566501930
59241e3f40b7
7badcd5adbee
426d6f1c1fe4
5621c90969ab
02e700896f2f
e8adf69bc6ca
287fd8542ffb
17635d4d1428
3c749bf8a173
0f0b05d6f100
6409f7f156aa
390df237aa65
3335cbb61d70
982311cc423d
54c5feb2973e
c0b841ffb837
2feaf8dd5499
f4009b857832
dd79f9d67588
4f0a90277d2f
f1c8b55a2502
42f24b2026e1
3f289cb0047c
286af87ebfc5
94786a77cf31
c099e5add2d9
1d959bcf86fa
e763a832022a
ce101d60593f
462f29453c20
f236b6442021
290f015fdc97
0b11dfa3ed58
543e4f9e5db1
505a4a2733c6
21c2ab103cd8
9070ee8cd4b2
4e4c0ae1f454
1a1c7f34b275
6f70b7df4731
61d50d22a899
da6299770b91
22b1a77738f9
caf3b3deb04b
542afd2937b0
6e979a4fbe81
d77aa18ccae6
9a48cf32b833
da985220afd1
7db747652cc2
36e00580a345
1ea7f0de3c1a
c55221aaf4a4
32ac0494cc54
f488d1dafda1
e959be72ef9c
c0236775d5d9
327cff468e44
b035c6eea11d
d4566949e02a
c5e534a45ef4
636544c45eec
03d0b5385df3
47dc81e0b079
73b3287ce6c7
8774232b2e3c
f364acb3684f
e76bbba9301f
44c778591fdd
1ba5b5cd3f42
406e2e8a1f19
34f9f23cff3c
b2f93daa7493
c5b9bceb2b12
71639f2faafc
cc5ab622811a
513168a1dcde
b2849633500b
7e6b629b66f8
286af87ebfc5
aa470bfa7df6
cdbb1652c1a7
c13b45d4189f
69873d0e7941
dfb8e4c872b7
2ba2540d28f2
796783193f6c
93114272db03
c3ab5a46bf1c
80f95d7ddf09
1505038fe995
629b20c24ac3
540f30bc9c84
82d467da2f6c
e1983c47dce8
285780180da0
5a355393b474
1db7fba288c2
2f53b310fd81
321958c442cb
ae00dbcf3671
28c158baf9b6
8747d14216e3
2a5cd454b4ce
6d647c89c95f
ced97eda7612
b3d1b8ecf60c
ca80df0c91bf
3483b78709f0
7e94b2a0d111
d6f0d4a50853
008ebb838fe0
832a15c56fc0
ffba0dbfd3c0
4ff48312d8c4
c9472559da6d
270d38c3ece6
75fdddc25da9
7ff80a1daafb
fbebf377d4c5
b1b8a2886d32
453798db94c1
339d91699389
db9452531926
404a60b4f609
16d16a618a39
ef4e8bcc34ec
e9c4e1ec2380
6db44ba81241
4535e6a06a51
878fc5c0d95f
8e0ce07ae4e0
c4867538d0e2
f7a40c7246c3
1315553b417f
5e5f4b4f02e2
9ecec34e955b
e3eff77bfa24
2bf8ec5e8017
808a82e8abac
2728e8dae954
778c836baf23
d1bdc1e5d7bc
b567af3a029f
954654d3f3b5
9a055e87611b
4a5ada77e1f7
5cec15508574
806f84d45821
e9eb1ec9071f
cd942103c944
c0885e1ee888
e30ef9672c72
adc753185dd7
374bd6d8a767
a5f07e7b2105
7c20d113df32
94f87020ee33
a5835b05e01d
798e125d61fd
1840351b5196
3b0ef6dc9db1
8daa1dd072d6
68739afaebf4
768bd47cca61
734b8a40e747