GNUtools/bison/INSTALL - annotate

Return to INSTALL CVS log

Up to [Apple XNU] / GNUtools / bison

Annotation of GNUtools/bison/INSTALL, revision 1.1.1.1

1.1 root 1: This is a generic INSTALL file for utilities distributions.
2: If this package does not come with, e.g., installable documentation or
3: data files, please ignore the references to them below.
4:
5: To compile this package:
6:
7: 1. Configure the package for your system. In the directory that this
8: file is in, type `./configure'. If you're using `csh' on an old
9: version of System V, you might need to type `sh configure' instead to
10: prevent `csh' from trying to execute `configure' itself.
11:
12: The `configure' shell script attempts to guess correct values for
13: various system-dependent variables used during compilation, and
14: creates the Makefile(s) (one in each subdirectory of the source
15: directory). In some packages it creates a C header file containing
16: system-dependent definitions. It also creates a file `config.status'
17: that you can run in the future to recreate the current configuration.
18:
19: Running `configure' takes a minute or two. While it is running, it
20: prints some messages that tell what it is doing. If you don't want to
21: see the messages, run `configure' with its standard output redirected
22: to `/dev/null'; for example, `./configure >/dev/null'.
23:
24: To compile the package in a different directory from the one
25: containing the source code, you must use a version of `make' that
26: supports the VPATH variable, such as GNU `make'. `cd' to the directory
27: where you want the object files and executables to go and run
28: `configure'. `configure' automatically checks for the source code in
29: the directory that `configure' is in and in `..'. If for some reason
30: `configure' is not in the source code directory that you are
31: configuring, then it will report that it can't find the source code.
32: In that case, run `configure' with the option `--srcdir=DIR', where
33: DIR is the directory that contains the source code.
34:
35: By default, `make install' will install the package's files in
36: /usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify an
37: installation prefix other than /usr/local by giving `configure' the option
38: `--prefix=PATH'. Alternately, you can do so by consistently giving a value
39: for the `prefix' variable when you run `make', e.g.,
40: make prefix=/usr/gnu
41: make prefix=/usr/gnu install
42:
43: You can specify separate installation prefixes for
44: architecture-specific files and architecture-independent files. If
45: you give `configure' the option `--exec-prefix=PATH' or set the
46: `make' variable `exec_prefix' to PATH, the package will use PATH as
47: the prefix for installing programs and libraries. Data files and
48: documentation will still use the regular prefix. Normally, all files
49: are installed using the regular prefix.
50:
51: Another `configure' option is useful mainly in `Makefile' rules for
52: updating `config.status' and `Makefile'. The `--no-create' option
53: figures out the configuration for your system and records it in
54: `config.status', without actually configuring the package (creating
55: `Makefile's and perhaps a configuration header file). Later, you can
56: run `./config.status' to actually configure the package. You can also
57: give `config.status' the `--recheck' option, which makes it re-run
58: `configure' with the same arguments you used before. This option is
59: useful if you change `configure'.
60:
61: Some packages pay attention to `--with-PACKAGE' options to `configure',
62: where PACKAGE is something like `gnu-libc' or `x' (for the X Window System).
63: The README should mention any --with- options that the package recognizes.
64:
65: `configure' ignores any other arguments that you give it.
66:
67: If your system requires unusual options for compilation or linking
68: that `configure' doesn't know about, you can give `configure' initial
69: values for some variables by setting them in the environment. In
70: Bourne-compatible shells, you can do that on the command line like
71: this:
72: CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
73:
74: The `make' variables that you might want to override with environment
75: variables when running `configure' are:
76:
77: (For these variables, any value given in the environment overrides the
78: value that `configure' would choose:)
79: CC C compiler program.
80: Default is `cc', or `gcc' if `gcc' is in your PATH.
81: INSTALL Program to use to install files.
82: Default is `install' if you have it, `cp' otherwise.
83:
84: (For these variables, any value given in the environment is added to
85: the value that `configure' chooses:)
86: DEFS Configuration options, in the form `-Dfoo -Dbar ...'
87: Do not use this variable in packages that create a
88: configuration header file.
89: LIBS Libraries to link with, in the form `-lfoo -lbar ...'
90:
91: If you need to do unusual things to compile the package, we encourage
92: you to figure out how `configure' could check whether to do them, and
93: mail diffs or instructions to the address given in the README so we
94: can include them in the next release.
95:
96: 2. Type `make' to compile the package. If you want, you can override
97: the `make' variables CFLAGS and LDFLAGS like this:
98:
99: make CFLAGS=-O2 LDFLAGS=-s
100:
101: 3. If the package comes with self-tests and you want to run them,
102: type `make check'. If you're not sure whether there are any, try it;
103: if `make' responds with something like
104: make: *** No way to make target `check'. Stop.
105: then the package does not come with self-tests.
106:
107: 4. Type `make install' to install programs, data files, and
108: documentation.
109:
110: 5. You can remove the program binaries and object files from the
111: source directory by typing `make clean'. To also remove the
112: Makefile(s), the header file containing system-dependent definitions
113: (if the package uses one), and `config.status' (all the files that
114: `configure' created), type `make distclean'.
115:
116: The file `configure.in' is used as a template to create `configure' by
117: a program called `autoconf'. You will only need it if you want to
118: regenerate `configure' using a newer version of `autoconf'.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.