Requirements
------------
You will need a C++98 compiler with support for 'long long', and the
compression library lzlib installed. (gcc 3.3.6 or newer is recommended).
I use gcc 6.1.0 and 3.3.6, but the code should compile with any standards
compliant compiler.

Lzlib must be version 1.12 or newer.

Gcc is available at http://gcc.gnu.org.
Lzlib is available at http://www.nongnu.org/lzip/lzlib.html.

The operating system must allow signal handlers read access to objects with
static storage duration so that the cleanup handler for Control-C can delete
the partial output file in '-z, --compress' mode.


Procedure
---------
1. Unpack the archive if you have not done so already:

	tar -xf tarlz[version].tar.lz
or
	lzip -cd tarlz[version].tar.lz | tar -xf -

This creates the directory ./tarlz[version] containing the source from
the main archive.

2. Change to tarlz directory and run configure.
   (Try 'configure --help' for usage instructions).

	cd tarlz[version]
	./configure

   To link against a lzlib not installed in a standard place, use:

	./configure CPPFLAGS='-I <includedir>' LDFLAGS='-L <libdir>'

   (Replace <includedir> with the directory containing the file lzlib.h,
            and <libdir> with the directory containing the file liblz.a).

3. Run make.

	make

4. Optionally, type 'make check' to run the tests that come with tarlz.

5. Type 'make install' to install the program and any data files and
   documentation.

   Or type 'make install-compress', which additionally compresses the
   info manual and the man page after installation.
   (Installing compressed docs may become the default in the future).

   You can install only the program, the info manual, or the man page by
   typing 'make install-bin', 'make install-info', or 'make install-man'
   respectively.


Another way
-----------
You can also compile tarlz into a separate directory.
To do this, you must use a version of 'make' that supports the variable
'VPATH', 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
explained above.


Copyright (C) 2013-2022 Antonio Diaz Diaz.

This file is free documentation: you have unlimited permission to copy,
distribute, and modify it.