![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to INSTALL CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / g / usr / bin / gzip|
Return to INSTALL CVS log | Up to [MW Coherent from dump] / coherent / g / usr / bin / gzip |
1.1 root 1: This is a generic INSTALL file for utilities distributions.
2: Some features specific to gzip have been added.
3:
4: To compile this package:
5:
6: 1. Configure the package for your system. In the directory that this
7: file is in, type `./configure'. If you're using `csh' on an old
8: version of System V, you might need to type `sh configure' instead to
9: prevent `csh' from trying to execute `configure' itself.
10:
11: The `configure' shell script attempts to guess correct values for
12: various system-dependent variables used during compilation, and
13: creates the Makefile(s) (one in each subdirectory of the source
14: directory). In some packages it creates a C header file containing
15: system-dependent definitions. It also creates a file `config.status'
16: that you can run in the future to recreate the current configuration.
17:
18: Running `configure' takes a minute or two. While it is running, it
19: prints some messages that tell what it is doing. If you don't want to
20: see the messages, run `configure' with its standard output redirected
21: to `/dev/null'; for example, `./configure >/dev/null'.
22:
23: To compile the package in a different directory from the one
24: containing the source code, you must use a version of make that
25: supports the VPATH variable, such as GNU make. `cd' to the directory
26: where you want the object files and executables to go and run
27: `configure'. `configure' automatically checks for the source code in
28: the directory that `configure' is in and in `..'. If for some reason
29: `configure' is not in the source code directory that you are
30: configuring, then it will report that it can't find the source code.
31: In that case, run `configure' with the option `--srcdir=DIR', where
32: DIR is the directory that contains the source code.
33:
34: By default, `make install' will install the package's files in
35: /usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify
36: an installation prefix other than /usr/local by giving `configure' the
37: option `--prefix=PATH'. Alternately, you can do so by giving a value
38: for the `prefix' variable when you run `make', e.g.,
39: make prefix=/usr/gnu
40:
41: You can specify separate installation prefixes for
42: architecture-specific files and architecture-independent files. If
43: you give `configure' the option `--exec_prefix=PATH' or set the
44: `make' variable `exec_prefix' to PATH, the package will use PATH as
45: the prefix for installing programs and libraries. Data files and
46: documentation will still use the regular prefix. Normally, all files
47: are installed using the regular prefix.
48:
49: You can tell `configure' to figure out the configuration for your
50: system, and record it in `config.status', without actually configuring
51: the package (creating `Makefile's and perhaps a configuration header
52: file). To do this, give `configure' the `--no-create' option. Later,
53: you can run `./config.status' to actually configure the package. This
54: option is useful mainly in `Makefile' rules for updating `config.status'
55: and `Makefile'. You can also give `config.status' the `--recheck'
56: option, which makes it re-run `configure' with the same arguments you
57: used before. This is useful if you change `configure'.
58:
59: `configure' ignores any other arguments that you give it.
60:
61: If your system requires unusual options for compilation or linking
62: that `configure' doesn't know about, you can give `configure' initial
63: values for some variables by setting them in the environment. In
64: Bourne-compatible shells, you can do that on the command line like
65: this:
66: CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
67:
68: The `make' variables that you might want to override with environment
69: variables when running `configure' are:
70:
71: (For these variables, any value given in the environment overrides the
72: value that `configure' would choose:)
73: CC C compiler program.
74: Default is `cc', or `gcc' if `gcc' is in your PATH.
75: INSTALL Program to use to install files.
76: Default is `install' if you have it, `cp' otherwise.
77:
78: (For these variables, any value given in the environment is added to
79: the value that `configure' chooses:)
80: DEFS Configuration options, in the form `-Dfoo -Dbar ...'
81: LIBS Libraries to link with, in the form `-lfoo -lbar ...'
82:
83: If you need to do unusual things to compile the package, we encourage
84: you to figure out how `configure' could check whether to do them, and
85: mail diffs or instructions to the address given in the README so we
86: can include them in the next release.
87:
88: On Xenix, some preprocessors do not define M_XENIX. You may have to do:
89:
90: DEFS='-DM_XENIX' ./configure
91:
92: 2. Type `make' to compile the package. If you want, you can override
93: the `make' variables CFLAGS and LDFLAGS like this:
94:
95: make CFLAGS=-O2 LDFLAGS=-s
96:
97: Try this if you get an error such as "ld: No such file or directory for libg"
98: which means that your system is not correctly set up to handle the
99: default -g option.
100:
101: The man pages are installed by default with an extension `.1' (one).
102: If you want the extension `.l' (lower case L) use:
103:
104: make manext=l
105:
106: and change the files gunzip.1 and zcat.1 accordingly.
107:
108: 3. The package comes with self-tests. If you want to run them,
109: type `make check'.
110:
111: 4. Type `make install' to install programs, data files, and
112: documentation. This creates links between gzip, gunzip and zcat.
113: You can create additional links uncompress, ungzip and gzcat if
114: you prefer these names. You can also create links to unpack and pcat
115: if your system uses packed files by default and you want to transform
116: them transparently to gzip'ed files.
117:
118: 5. You can remove the program binaries and object files from the
119: source directory by typing `make clean'. To also remove the
120: Makefile(s), the header file containing system-dependent definitions
121: (if the package uses one), and `config.status' (all the files that
122: `configure' created), type `make distclean'.
123:
124: The file `configure.in' is used as a template to create `configure' by
125: a program called `autoconf'. You will only need it if you want to
126: regenerate `configure' using a newer version of `autoconf'.
127: Some bugs in autoconf have been fixed before generating `configure',
128: so you may not get exactly the same output.
129:
130: 6. You can add the following lines to your /etc/magic file so that
131: file(1), if your system supports it, will recognize files created by
132: gzip:
133:
134: 0 short 0x1f8b gzip compressed data
135: >2 byte 8 - deflate method
136: >3 byte &0x1 , ascii
137: >3 byte &0x2 , continuation
138: >3 byte &0x4 , extra field
139: >3 byte &0x8 , original file name
140: >3 byte &0x10 , comment
141: >3 byte &0x20 , encrypted
142:
143: If your machine is a 386 or a Vax (little-endian machine), replace the
144: first line with:
145:
146: 0 short 0x8b1f gzip compressed data
147:
148: There is no portable way working on both little-endian and
149: big-endian machines, since SVR4 does not like the string \037\213
150: as a magic number.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.