source: trunk/mondo/INSTALL

Last change on this file was 1079, checked in by bruno, 12 years ago

merge -r1045:1078 £SVN_M/branches/stable

  • Property svn:keywords set to Id
File size: 7.3 KB
Line 
1Basic Installation
2==================
3
4gzip -dc mondo-x.xx.tar.gz | tar -xvf-
5cd mondo-x.xx
6./configure <args-to-configure>
7make
8make install
9
10<args-to-configure> can be blank if your needs are simple. If not, read
11configure --help. Example: use --prefix=/usr to install in /usr instead
12of /usr/local. If you have extreme needs and 50 media isn't enough,
13configure --with-maximum-noof-media=<big-number>. To make a statically
14linked mondorestore (not tested), configure --enable-static-mr.
15
16[original entry]
17
18   These are generic installation instructions.
19
20   The `configure' shell script attempts to guess correct values for
21various system-dependent variables used during compilation.  It uses
22those values to create a `Makefile' in each directory of the package.
23It may also create one or more `.h' files containing system-dependent
24definitions.  Finally, it creates a shell script `config.status' that
25you can run in the future to recreate the current configuration, a file
26`config.cache' that saves the results of its tests to speed up
27reconfiguring, and a file `config.log' containing compiler output
28(useful mainly for debugging `configure').
29
30   If you need to do unusual things to compile the package, please try
31to figure out how `configure' could check whether to do them, and mail
32diffs or instructions to the address given in the `README' so they can
33be considered for the next release.  If at some point `config.cache'
34contains results you don't want to keep, you may remove or edit it.
35
36   The file `configure.in' is used to create `configure' by a program
37called `autoconf'.  You only need `configure.in' if you want to change
38it or regenerate `configure' using a newer version of `autoconf'.
39
40The 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 a while.  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. Type `make install' to install the programs and any data files and
54     documentation.
55
56  4. You can remove the program binaries and object files from the
57     source code directory by typing `make clean'. 
58
59Compilers and Options
60=====================
61
62   Some systems require unusual options for compilation or linking that
63the `configure' script does not know about.  You can give `configure'
64initial values for variables by setting them in the environment.  Using
65a Bourne-compatible shell, you can do that on the command line like
66this:
67     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
68
69Or on systems that have the `env' program, you can do it like this:
70     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
71
72Compiling For Multiple Architectures
73====================================
74
75   You can compile the package for more than one kind of computer at the
76same time, by placing the object files for each architecture in their
77own directory.  To do this, you must use a version of `make' that
78supports the `VPATH' variable, such as GNU `make'.  `cd' to the
79directory where you want the object files and executables to go and run
80the `configure' script.  `configure' automatically checks for the
81source code in the directory that `configure' is in and in `..'.
82
83   If you have to use a `make' that does not supports the `VPATH'
84variable, you have to compile the package for one architecture at a time
85in the source code directory.  After you have installed the package for
86one architecture, use `make distclean' before reconfiguring for another
87architecture.
88
89Installation Names
90==================
91
92   By default, `make install' will install the package's files in
93`/usr/local/bin', `/usr/local/man', etc.  You can specify an
94installation prefix other than `/usr/local' by giving `configure' the
95option `--prefix=PATH'.
96
97   You can specify separate installation prefixes for
98architecture-specific files and architecture-independent files.  If you
99give `configure' the option `--exec-prefix=PATH', the package will use
100PATH as the prefix for installing programs and libraries.
101Documentation and other data files will still use the regular prefix.
102
103   If the package supports it, you can cause programs to be installed
104with an extra prefix or suffix on their names by giving `configure' the
105option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
106
107Optional Features
108=================
109
110   Some packages pay attention to `--enable-FEATURE' options to
111`configure', where FEATURE indicates an optional part of the package.
112They may also pay attention to `--with-PACKAGE' options, where PACKAGE
113is something like `gnu-as' or `x' (for the X Window System).  The
114`README' should mention any `--enable-' and `--with-' options that the
115package recognizes.
116
117   For packages that use the X Window System, `configure' can usually
118find the X include and library files automatically, but if it doesn't,
119you can use the `configure' options `--x-includes=DIR' and
120`--x-libraries=DIR' to specify their locations.
121
122Specifying the System Type
123==========================
124
125   There may be some features `configure' can not figure out
126automatically, but needs to determine by the type of host the package
127will run on.  Usually `configure' can figure that out, but if it prints
128a message saying it can not guess the host type, give it the
129`--host=TYPE' option.  TYPE can either be a short name for the system
130type, such as `sun4', or a canonical name with three fields:
131     CPU-COMPANY-SYSTEM
132
133See the file `config.sub' for the possible values of each field.  If
134`config.sub' isn't included in this package, then this package doesn't
135need to know the host type.
136
137   If you are building compiler tools for cross-compiling, you can also
138use the `--target=TYPE' option to select the type of system they will
139produce code for and the `--build=TYPE' option to select the type of
140system on which you are compiling the package.
141
142Sharing Defaults
143================
144
145   If you want to set default values for `configure' scripts to share,
146you can create a site shell script called `config.site' that gives
147default values for variables like `CC', `cache_file', and `prefix'.
148`configure' looks for `PREFIX/share/config.site' if it exists, then
149`PREFIX/etc/config.site' if it exists.  Or, you can set the
150`CONFIG_SITE' environment variable to the location of the site script.
151A warning: not all `configure' scripts look for a site script.
152
153Operation Controls
154==================
155
156   `configure' recognizes the following options to control how it
157operates.
158
159`--cache-file=FILE'
160     Use and save the results of the tests in FILE instead of
161     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
162     debugging `configure'.
163
164`--help'
165     Print a summary of the options to `configure', and exit.
166
167`--quiet'
168`--silent'
169`-q'
170     Do not print messages saying which checks are being made.
171
172`--srcdir=DIR'
173     Look for the package's source code in directory DIR.  Usually
174     `configure' can determine that directory automatically.
175
176`--version'
177     Print the version of Autoconf used to generate the `configure'
178     script, and exit.
179
180`configure' also accepts some other, not widely useful, options.
181
Note: See TracBrowser for help on using the repository browser.