Basic Installation==================These are installation instructions for Readline-4.3.The simplest way to compile readline is:  1. `cd' to the directory containing the readline source code and type     `./configure' to configure readline for your system.  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 some time.  While running, it prints some     messages telling which features it is checking for.  2. Type `make' to compile readline and build the static readline     and history libraries.  If supported, the shared readline and history     libraries will be built also.  See below for instructions on compiling     the other parts of the distribution.  Typing `make everything' will     cause the static and shared libraries (if supported) and the example     programs to be built.  3. Type `make install' to install the static readline and history     libraries, the readline include files, the documentation, and, if     supported, the shared readline and history libraries.  4. You can remove the created libraries and object files from the     build directory by typing `make clean'.  To also remove the     files that `configure' created (so you can compile readline for     a different kind of computer), type `make distclean'.  There is     also a `make maintainer-clean' target, but that is intended mainly     for the readline developers, and should be used with care.The `configure' shell script attempts to guess correct values forvarious system-dependent variables used during compilation.  Ituses those values to create a `Makefile' in the build directory,and Makefiles in the `doc', `shlib', and `examples'subdirectories.  It also creates a `config.h' file containingsystem-dependent definitions.  Finally, it creates a shell script`config.status' that you can run in the future to recreate thecurrent configuration, a file `config.cache' that saves theresults of its tests to speed up reconfiguring, and a file`config.log' containing compiler output (useful mainly fordebugging `configure'). If you need to do unusual things to compile readline, please tryto figure out how `configure' could check whether to do them, andmail diffs or instructions to <bug-readline@gnu.org> so they canbe considered for the next release.  If at some point`config.cache' contains results you don't want to keep, you mayremove or edit it. The file `configure.in' is used to create `configure' by aprogram called `autoconf'.  You only need `configure.in' if youwant to change it or regenerate `configure' using a newer versionof `autoconf'.  The readline `configure.in' requires autoconfversion 2.50 or newer. Compilers and Options=====================Some systems require unusual options for compilation or linking thatthe `configure' script does not know about.  You can give `configure'initial values for variables by setting them in the environment.  Usinga Bourne-compatible shell, you can do that on the command line likethis:     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configureOr on systems that have the `env' program, you can do it like this:     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configureCompiling For Multiple Architectures====================================You can compile readline for more than one kind of computer at thesame time, by placing the object files for each architecture in theirown directory.  To do this, you must use a version of `make' thatsupports the `VPATH' variable, such as GNU `make'.  `cd' to thedirectory where you want the object files and executables to go and runthe `configure' script.  `configure' automatically checks for thesource code in the directory that `configure' is in and in `..'.If you have to use a `make' that does not supports the `VPATH'variable, you have to compile readline for one architecture at atime in the source code directory.  After you have installedreadline for one architecture, use `make distclean' beforereconfiguring for another architecture. Installation Names==================By default, `make install' will install the readline libraries in`/usr/local/lib', the include files in`/usr/local/include/readline', the man pages in `/usr/local/man',and the info files in `/usr/local/info'.  You can specify aninstallation prefix other than `/usr/local' by giving `configure'the option `--prefix=PATH' or by supplying a value for theDESTDIR variable when running `make install'. You can specify separate installation prefixes forarchitecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', thereadline Makefiles will use PATH as the prefix for installing thelibraries.  Documentation and other data files will still use theregular prefix. Specifying the System Type==========================There may be some features `configure' can not figure outautomatically, but need to determine by the type of host readlinewill run on.  Usually `configure' can figure that out, but if itprints a message saying it can not guess the host type, give itthe `--host=TYPE' option.  TYPE can either be a short name forthe system type, such as `sun4', or a canonical name with threefields: CPU-COMPANY-SYSTEM (e.g., i386-unknown-freebsd4.2). See the file `config.sub' for the possible values of each field.Sharing Defaults================If you want to set default values for `configure' scripts to share,you can create a site shell script called `config.site' that givesdefault values for variables like `CC', `cache_file', and `prefix'.`configure' looks for `PREFIX/share/config.site' if it exists, then`PREFIX/etc/config.site' if it exists.  Or, you can set the`CONFIG_SITE' environment variable to the location of the site script.A warning: the readline `configure' looks for a site script, but notall `configure' scripts do.Operation Controls==================`configure' recognizes the following options to control how itoperates.`--cache-file=FILE'     Use and save the results of the tests in FILE instead of     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for     debugging `configure'.`--help'     Print a summary of the options to `configure', and exit.`--quiet'`--silent'`-q'     Do not print messages saying which checks are being made.`--srcdir=DIR'     Look for the package's source code in directory DIR.  Usually     `configure' can determine that directory automatically.`--version'     Print the version of Autoconf used to generate the `configure'     script, and exit.`configure' also accepts some other, not widely useful, options.Optional Features=================The readline `configure' recognizes a single `--with-PACKAGE' option:`--with-curses'    This tells readline that it can find the termcap library functions    (tgetent, et al.) in the curses library, rather than a separate    termcap library.  Readline uses the termcap functions, but does not    link with the termcap or curses library itself, allowing applications    which link with readline the to choose an appropriate library.    This option tells readline to link the example programs with the    curses library rather than libtermcap.`configure' also recognizes two `--enable-FEATURE' options:`--enable-shared'    Build the shared libraries by default on supported platforms.  The    default is `yes'.`--enable-static'    Build the static libraries by default.  The default is `yes'. Shared Libraries================There is support for building shared versions of the readline andhistory libraries.  The configure script creates a Makefile inthe `shlib' subdirectory, and typing `make shared' will causeshared versions of the readline and history libraries to be builton supported platforms.If `configure' is given the `--enable-shared' option, it will attemptto build the shared libraries by default on supported platforms.Configure calls the script support/shobj-conf to test whether ornot shared library creation is supported and to generate the valuesof variables that are substituted into shlib/Makefile.  If youtry to build shared libraries on an unsupported platform, `make'will display a message asking you to update support/shobj-conf foryour platform.If you need to update support/shobj-conf, you will need to createa `stanza' for your operating system and compiler.  The script usesthe value of host_os and ${CC} as determined by configure.  Forinstance, FreeBSD 4.2 with any version of gcc is identified as`freebsd4.2-gcc*'.In the stanza for your operating system-compiler pair, you will need todefine several variables.  They are:SHOBJ_CC	The C compiler used to compile source files into shareable		object files.  This is normally set to the value of ${CC}		by configure, and should not need to be changed.SHOBJ_CFLAGS	Flags to pass to the C compiler ($SHOBJ_CC) to create		position-independent code.  If you are using gcc, this		should probably be set to `-fpic'.SHOBJ_LD	The link editor to be used to create the shared library from		the object files created by $SHOBJ_CC.  If you are using		gcc, a value of `gcc' will probably work.SHOBJ_LDFLAGS	Flags to pass to SHOBJ_LD to enable shared object creation.		If you are using gcc, `-shared' may be all that is necessary.		These should be the flags needed for generic shared object		creation.SHLIB_XLDFLAGS	Additional flags to pass to SHOBJ_LD for shared library		creation.  Many systems use the -R option to the link		editor to embed a path within the library for run-time		library searches.  A reasonable value for such systems would		be `-R$(libdir)'.SHLIB_LIBS	Any additional libraries that shared libraries should be		linked against when they are created.SHLIB_LIBSUFF	The suffix to add to `libreadline' and `libhistory' when		generating the filename of the shared library.  Many systems		use `so'; HP-UX uses `sl'.SHLIB_LIBVERSION The string to append to the filename to indicate the version		of the shared library.  It should begin with $(SHLIB_LIBSUFF),		and possibly include version information that allows the		run-time loader to load the version of the shared library		appropriate for a particular program.  Systems using shared		libraries similar to SunOS 4.x use major and minor library		version numbers; for those systems a value of		`$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)$(SHLIB_MINOR)' is appropriate.		Systems based on System V Release 4 don't use minor version		numbers; use `$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)' on those systems.		Other Unix versions use different schemes.SHLIB_STATUS	Set this to `supported' when you have defined the other		necessary variables.  Make uses this to determine whether		or not shared library creation should be attempted.  If		shared libraries are not supported, this will be set to		`unsupported'.You should look at the existing stanzas in support/shobj-conf for ideas.Once you have updated support/shobj-conf, re-run configure and type`make shared' or `make'.  The shared libraries will be created in theshlib subdirectory.If shared libraries are created, `make install' will install them. You may install only the shared libraries by running `makeinstall-shared' from the top-level build directory.  Running `makeinstall' in the shlib subdirectory will also work.  If you don't wantto install any created shared libraries, run `make install-static'.