Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
286 lines (213 sloc) 10.9 KB
1. Basic Installation
1.1 Compilers and Options
1.2.1 Compiling For Multiple Architectures
1.2 Installation Names
1.3 Optional Features
1.4 Specifying the System Type
1.5 Sharing Defaults
1.6 Operation Controls
2. EMBOSS Customisation
2.1 The emboss.defaults file
2.1.1 SET variables
1. 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 `' is used to create `configure' by a program
called `autoconf'. You only need `' 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 a while. 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
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.
1.1 Compilers and Options
The `configure' script will check for the GNU C compiler (gcc), but
will use your usual (cc) compiler if gcc is not found. You can tell
configure to use the `cc' compiler by adding the following line after
the first line of `configure' :
or by this csh command:
setenv CC cc
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
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
1.2.1 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
1.2 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'.
1.3 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.
1.4 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:
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.
1.5 Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' 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.
1.6 Operation Controls
`configure' recognizes the following options to control how it
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'.
Print a summary of the options to `configure', and exit.
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).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
2. EMBOSS Customisation
2.1 The emboss.default file
EMBOSS programs read two files on startup to define control variables
and biological databases. The system-wide file is "emboss.default" which
should be in the install directory under share/EMBOSS/emboss.default
A template version emboss.default.template is installed in the same
directory. Site administrators should check new versions of this
file for changes in a new release. The original template file is in
the distribution under the emboss directory.
There are 2 types of definition in the emboss.default file.
2.1.1 SET variables
EMBOSS uses environment variables for various controls. They all
are uppercase names, and have the prefix "EMBOSS_". Usually these
are defined in the emboss.defaults file, where case is not
significant. The syntax is:
SET <emboss_variable> "<valuestring>"
The most useful are:
EMBOSS_LOGFILE A file that will log all EMBOSS usage (program,
user, date). You should uncomment this line and cteate the file.
EMBOSS_TEMPDATA The dirctory where the test subdirectory
databases are installed (See TEMBL and other databases below).
Only needed if you use the TEMBL (etc.) definitions that use
2.1.2 DB database definitions
EMBOSS sequence databases are defined as "DB" structures in the
emboss.default file. You can define as many databases as you
need. All databases must have a name, a type, a format and a
method. Many of the fields are optional.
The syntax is:
DB <name> [ type: <type> format: <format> method: <method>
<attribute>: <attr_value>
The name is the name used in EMBOSS USAs.
Type is P for protein, or N for nucleotide.
Method is the access method used to query or read the database
Some databases can have multiple access methods, though this is
less common with later EMBOSS versions. The main use now is with
the SRS access method, which uses SRS's getz command but cannot
read the whole database. In this case, "methodall" can be used to
define an alternative access method to read the original data
files. You can also define "methodentry" for a single ID
query, and "methodquery" for all other searches.
Format is the sequence format returned by the acces method. For a
list of known input formats, see:
Something went wrong with that request. Please try again.