configure
script generated with
GNU
Autoconf, these instructions are based on the generic
installation instructions that come with Autoconf. The
following topics are covered:
./configure
make
make install
configure
shell script.
configure
attempts to guess correct values for various
system-dependent variables used during compilation, including
sub-system dependencies.
configure
can find the C++ compiler
in your current path. However you can also specify one particular
compiler by setting the CXX
environment variable. E.g.:
setenv CXX /opt/c++/bin/c++
configure
looks for the gdbm library in the
default include and library directories. You can direct
configure
to the right paths by using the following
command-line switces:
--with-gdbm-include=
dir--with-gdbm-libdir=
dirconfigure
looks for the pthread library in the default
include and library directories. You can direct
configure
to the right paths by using the followin
command-line switces:
--with-pthreads-include=
dir--with-pthreads-libdir=
dir--with-pthreads-libs=
librariespthreads
libraries (default=-lpthread
)
cd
into the build directory
CXX
to your C++
compiler
configure
. If necessary, specify an installation
prefix and various includes and library paths (see Dependencies above):
SRCDIR/configure --prefix=/usr/tools
make
make install
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
.
If you have any problem configuring, building, or installing Siena,
please contact Antonio
Carzaniga.
What follows is a set of generic instructions for using the
configure
script.
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 ./configureOr on systems that have the
env
program, you can do it like this:
env CPPFLAGS=-I/opt/include LDFLAGS=-s ./configure
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.
make install
will install the package's
files in /opt/bin
, /opt/man
, etc. You can
specify an installation prefix other than /opt
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
.
--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.
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.
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.
configure
recognizes the following options to control
how it operates.
--cache-file=FILE
./config.cache
. Set FILE
to /dev/null
to disable caching, for debugging
configure
.
--help
configure
, and exit.
--quiet
, --silent
, or -q
/dev/null
(any error
messages will still be shown).
--srcdir=DIR
configure
can determine
that directory automatically.
--version
configure
script, and exit.
configure
also accepts some other, not widely useful,
options.