Non-generic version.
This commit is contained in:
mainzelm
parent
f0584e822b
commit
125636a758
133
INSTALL
133
INSTALL
|
|
@ -1,120 +1,49 @@
|
||||||
This is a generic INSTALL file for utilities distributions.
|
Installing scsh
|
||||||
If this package does not come with, e.g., installable documentation or
|
|
||||||
data files, please ignore the references to them below.
|
|
||||||
|
|
||||||
[For information specific to Scheme 48, see doc/install.txt.]
|
This file describes how to install scsh from the source package. If
|
||||||
|
you have obtained the source tree from CVS refer to the file
|
||||||
The `configure' shell script attempts to guess correct values for
|
CVS_README.
|
||||||
various system-dependent variables used during compilation, and
|
|
||||||
creates the Makefile(s) (one in each subdirectory of the source
|
|
||||||
directory). In some packages it creates a C header file containing
|
|
||||||
system-dependent definitions. It also creates a file `config.status'
|
|
||||||
that you can run in the future to recreate the current configuration.
|
|
||||||
|
|
||||||
To compile this package:
|
|
||||||
|
|
||||||
1. Configure the package for your system.
|
1. Configure the package for your system.
|
||||||
|
|
||||||
Normally, you just `cd' to the directory containing the package's
|
Just `cd' to the directory containing this README file and type
|
||||||
source code and type `./configure'. 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 minute or two. While it is running, it
|
./configure
|
||||||
prints some messages that tell what it is doing. If you don't want to
|
|
||||||
see the messages, run `configure' with its standard output redirected
|
|
||||||
to `/dev/null'; for example, `./configure >/dev/null'.
|
|
||||||
|
|
||||||
To compile the package in a different directory from the one
|
You can pass some additional options to the configure script, along
|
||||||
containing the source code, you must use a version of `make' that
|
them the installation directory with the
|
||||||
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
--prefix=/my/install/location option. Type ./configure --help to
|
||||||
directory where you want the object files and executables to go and run
|
get a list of all switches.
|
||||||
the `configure' script. `configure' automatically checks for the
|
Running `configure' takes a minute or two. While it is running, it
|
||||||
source code in the directory that `configure' is in and in `..'. If
|
prints some messages that tell what it is doing. Consult the file
|
||||||
for some reason `configure' is not in the source code directory that
|
config.log if anything went wrong.
|
||||||
you are configuring, then it will report that it can't find the source
|
|
||||||
code. In that case, run `configure' with the option `--srcdir=DIR',
|
|
||||||
where DIR is the directory that contains the source code.
|
|
||||||
|
|
||||||
By default, `make install' will install the package's files in
|
2. Type
|
||||||
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
|
||||||
installation prefix other than `/usr/local' by giving `configure' the
|
|
||||||
option `--prefix=PATH'. Alternately, you can do so by consistently
|
|
||||||
giving a value for the `prefix' variable when you run `make', e.g.,
|
|
||||||
make prefix=/usr/gnu
|
|
||||||
make prefix=/usr/gnu install
|
|
||||||
|
|
||||||
You can specify separate installation prefixes for
|
make
|
||||||
architecture-specific files and architecture-independent files. If you
|
|
||||||
give `configure' the option `--exec-prefix=PATH' or set the `make'
|
|
||||||
variable `exec_prefix' to PATH, the package will use PATH as the prefix
|
|
||||||
for installing programs and libraries. Data files and documentation
|
|
||||||
will still use the regular prefix. Normally, all files are installed
|
|
||||||
using the same prefix.
|
|
||||||
|
|
||||||
Some packages pay attention to `--with-PACKAGE' options to
|
to compile scsh.
|
||||||
`configure', where PACKAGE is something like `gnu-as' or `x' (for the X
|
|
||||||
Window System). The README should mention any `--with-' options that
|
|
||||||
the package recognizes.
|
|
||||||
|
|
||||||
`configure' ignores any other arguments that you give it.
|
3. After a successful build you can invoke scsh by typing
|
||||||
|
|
||||||
On systems that require unusual options for compilation or linking
|
./go
|
||||||
that the package's `configure' script does not know about, you can give
|
|
||||||
`configure' initial values for variables by setting them in the
|
|
||||||
environment. In Bourne-compatible shells, you can do that on the
|
|
||||||
command line like this:
|
|
||||||
|
|
||||||
CC='gcc -traditional' LIBS=-lposix ./configure
|
You should see the command prompt of scsh which you can exit by
|
||||||
|
typing `,exit'.
|
||||||
|
|
||||||
Here are the `make' variables that you might want to override with
|
4. Type
|
||||||
environment variables when running `configure'.
|
|
||||||
|
|
||||||
For these variables, any value given in the environment overrides the
|
make install
|
||||||
value that `configure' would choose:
|
|
||||||
|
|
||||||
- Variable: CC
|
to install programs, data files, and documentation.
|
||||||
C compiler program. The default is `cc'.
|
|
||||||
|
|
||||||
- Variable: INSTALL
|
|
||||||
Program to use to install files. The default is `install' if you
|
|
||||||
have it, `cp' otherwise.
|
|
||||||
|
|
||||||
For these variables, any value given in the environment is added to
|
|
||||||
the value that `configure' chooses:
|
|
||||||
|
|
||||||
- Variable: DEFS
|
|
||||||
Configuration options, in the form `-Dfoo -Dbar...'. Do not use
|
|
||||||
this variable in packages that create a configuration header file.
|
|
||||||
|
|
||||||
- Variable: LIBS
|
|
||||||
Libraries to link with, in the form `-lfoo -lbar...'.
|
|
||||||
|
|
||||||
If you need to do unusual things to compile the package, we encourage
|
|
||||||
you to figure out how `configure' could check whether to do them, and
|
|
||||||
mail diffs or instructions to the address given in the README so we
|
|
||||||
can include them in the next release.
|
|
||||||
|
|
||||||
2. Type `make' to compile the package. If you want, you can override
|
|
||||||
the `make' variables CFLAGS and LDFLAGS like this:
|
|
||||||
|
|
||||||
make CFLAGS=-O2 LDFLAGS=-s
|
|
||||||
|
|
||||||
3. If the package comes with self-tests and you want to run them,
|
|
||||||
type `make check'. If you're not sure whether there are any, try it;
|
|
||||||
if `make' responds with something like
|
|
||||||
make: *** No way to make target `check'. Stop.
|
|
||||||
then the package does not come with self-tests.
|
|
||||||
|
|
||||||
4. Type `make install' to install programs, data files, and
|
|
||||||
documentation.
|
|
||||||
|
|
||||||
5. You can remove the program binaries and object files from the
|
5. You can remove the program binaries and object files from the
|
||||||
source directory by typing `make clean'. To also remove the
|
source directory by typing `make clean'. To also remove the
|
||||||
Makefile(s), the header file containing system-dependent definitions
|
Makefile, the header file containing system-dependent definitions
|
||||||
(if the package uses one), and `config.status' (all the files that
|
, `config.status' and `config.cache' (all the files that
|
||||||
`configure' created), type `make distclean'.
|
`configure' created), type `make distclean'.
|
||||||
|
|
||||||
The file `configure.in' is used to create `configure' by a program
|
For more information about scsh have a look into the README file and
|
||||||
called `autoconf'. You only need it if you want to regenerate
|
the documentation in the `doc/' directory. There you can also read
|
||||||
`configure' using a newer version of `autoconf'.
|
documentation about Scheme 48, the Scheme implementation scsh is based
|
||||||
|
on.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue