summaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL41
1 files changed, 27 insertions, 14 deletions
diff --git a/INSTALL b/INSTALL
index 8c25df2..18a372a 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,10 +1,19 @@
Requirements
------------
You will need a C++ compiler.
-I use gcc 4.3.5 and 3.3.6, but the code should compile with any
+I use gcc 4.7.2 and 3.3.6, but the code should compile with any
standards compliant compiler.
Gcc is available at http://gcc.gnu.org.
+If you are installing zutils along with GNU gzip and want to keep the
+gzip scripts, the recommended method is to configure gzip as follows:
+
+ ./configure --program-transform-name='s/^z/gz/'
+
+This renames, at installation time, the gzip scripts and man pages to
+'gzcat', 'gzcat.1', etc, avoiding the name clashing with the programs
+and man pages from zutils.
+
Procedure
---------
@@ -18,7 +27,7 @@ This creates the directory ./zutils[version] containing the source from
the main archive.
2. Change to zutils directory and run configure.
- (Try `configure --help' for usage instructions).
+ (Try 'configure --help' for usage instructions).
cd zutils[version]
./configure
@@ -27,30 +36,34 @@ the main archive.
make
-4. Optionally, type `make check' to run the tests that come with zutils.
+4. Optionally, type 'make check' to run the tests that come with zutils.
-5. Type `make install' to install the programs and any data files and
+5. Type 'make install' to install the programs and any data files and
documentation.
+ You can install only the programs, the info manual or the man pages
+ typing 'make install-bin', 'make install-info' or 'make install-man'
+ respectively.
+
Another way
-----------
You can also compile zutils into a separate 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 `.', in `..' and in the
-directory that `configure' is in.
-
-`configure' recognizes the option `--srcdir=DIR' to control where to
-look for the sources. Usually `configure' can determine that directory
+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 '.', in '..' and in the
+directory that 'configure' is in.
+
+'configure' recognizes the option '--srcdir=DIR' to control where to
+look for the sources. Usually 'configure' can determine that directory
automatically.
-After running `configure', you can run `make' and `make install' as
+After running 'configure', you can run 'make' and 'make install' as
explained above.
-Copyright (C) 2009, 2010, 2011 Antonio Diaz Diaz.
+Copyright (C) 2009, 2010, 2011, 2012, 2013 Antonio Diaz Diaz.
This file is free documentation: you have unlimited permission to copy,
distribute and modify it.