Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Diff of /INSTALL [000000] .. [942946] Maximize Restore

  Switch to unified view

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