a34b05d2e6
This opens an OpenBSD-mirabile (aka MirBSD) repository. ### MirBSD is: # Copyright (c) 1982-2003 by Thorsten "mirabile" Glaser <x86@ePost.de> # Copyright © 1968-2003 The authors of And contributors to UNIX®, the # C Language, BSD/Berkeley Unix; 386BSD, NetBSD 1.1 and OpenBSD. # # Anyone who obtained a copy of this work is hereby permitted to freely use, # distribute, modify, merge, sublicence, give away or sell it as long as the # authors are given due credit and the following notice is retained: # # This work is provided "as is", with no explicit or implicit warranty what- # soever. Use it only at your own risk. In no event may an author or contri- # butor be held liable for any damage, directly or indirectly, that origina- # ted through or is caused by creation or modification of this work. MirBSD is my private tree. MirBSD does not differ very much from OpenBSD and intentionally tracks OpenBSD. That's why it _is_ OpenBSD, just not the official one. It's like with DarrenBSD. At time of this writing, no advertising for MirBSD must be done, because the advertising clause has not yet been sorted out. http://templeofhate.com/tglaser/MirBSD/index.php
152 lines
6.1 KiB
Plaintext
152 lines
6.1 KiB
Plaintext
$OpenBSD: INSTALL,v 1.1.1.1 1996/08/14 06:19:10 downsj Exp $
|
|
|
|
[This file is the generic GNU autoconf/configure installation description,
|
|
see the README for pdksh specific configuration/installation information]
|
|
|
|
This is a generic INSTALL file for utilities distributions.
|
|
If this package does not come with, e.g., installable documentation or
|
|
data files, please ignore the references to them below.
|
|
|
|
The `configure' shell script attempts to guess correct values for
|
|
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.
|
|
|
|
Normally, you just `cd' to the directory containing the package's
|
|
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 awhile. While it is running, it
|
|
prints some messages that tell what it is doing. If you don't want to
|
|
see any 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
|
|
containing the source code, 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
|
|
for some reason `configure' is not in the source code directory that
|
|
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
|
|
`/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
|
|
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
|
|
`configure', where PACKAGE is something like `gnu-as' or `x' (for the
|
|
X Window System). They may also pay attention to `--enable-FEATURE'
|
|
options, where FEATURE indicates an optional part of the package. The
|
|
README should mention any `--with-' and `--enable-' options that the
|
|
package recognizes.
|
|
|
|
`configure' also recognizes the following options:
|
|
|
|
`--help'
|
|
Print a summary of the options to `configure', and exit.
|
|
|
|
`--quiet'
|
|
`--silent'
|
|
Do not print messages saying which checks are being made.
|
|
|
|
`--verbose'
|
|
Print the results of the checks.
|
|
|
|
`--version'
|
|
Print the version of Autoconf used to generate the `configure'
|
|
script, and exit.
|
|
|
|
`--x-includes=DIR'
|
|
X include files are in DIR.
|
|
|
|
`--x-libraries=DIR'
|
|
X library files are in DIR.
|
|
|
|
`configure' also accepts and ignores some other options.
|
|
|
|
On systems that require unusual options for compilation or linking
|
|
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
|
|
|
|
On systems that have the `env' program, you can do it like this:
|
|
|
|
env CC='gcc -traditional' LIBS=-lposix ./configure
|
|
|
|
Here are the `make' variables that you might want to override with
|
|
environment variables when running `configure'.
|
|
|
|
For these variables, any value given in the environment overrides the
|
|
value that `configure' would choose:
|
|
|
|
- Variable: CC
|
|
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
|
|
source directory by typing `make clean'. To also remove the
|
|
Makefile(s), the header file containing system-dependent definitions
|
|
(if the package uses one), and `config.status' (all the files that
|
|
`configure' created), type `make distclean'.
|
|
|
|
The file `configure.in' is used to create `configure' by a program
|
|
called `autoconf'. You only need it if you want to regenerate
|
|
`configure' using a newer version of `autoconf'.
|