--------------------------------------------
- Documentation version:  1.51-00
- Documentation date:  06/12/2004
- Parsing date: Mon Dec  6 22:12:20 CET 2004
--------------------------------------------
 

This file contains the TXT install instructions for Krusader.
This file is parsed from Docbook/XML source files.

After the TXT install instructions for Krusader you will find
generic installation instructions for KDE applications.

NOTE:
after the parsing process to generate this TXT file all te URL's are gone,
to see the URL's again please take a look at the HTML version of this file.

The HTML version of this file can be found at:      
http://krusader.sourceforge.net/handbook/installation.html

The HTML version of the FAQ can be found at:
http://krusader.sourceforge.net/handbook/faq.html

Feedback for the documentation is always welcome.

Frank Schoolmeesters, documentation coordinator
[frank_schoolmeesters {*} fastmail {.} fm]


Newer versions of the docmentation should always be available:
- online reading:
    http://krusader.sourceforge.net/handbook/index.html
- most recent tarball
    http://sourceforge.net/project/showfiles.php?group_id=6488
- when downloading and installing the most recent Krusader from the
    cvs repository (the doc's will be available via the Help menu) 


            as always, enjoy
                 Krusader Krew.

                      http://krusader.sourceforge.net
		      

db   dD d8888b. db    db .d8888.  .d8b.  d8888b. d88888b d8888b.
88 ,8P' 88  `8D 88    88 88'  YP d8' `8b 88  `8D 88'     88  `8D
88,8P   88oobY' 88    88 `8bo.   88ooo88 88   88 88ooooo 88oobY'
88`8b   88`8b   88    88   `Y8b. 88~~~88 88   88 88~~~~~ 88`8b
88 `88. 88 `88. 88b  d88 db   8D 88   88 88  .8D 88.     88 `88.
YP   YD 88   YD ~Y8888P' `8888Y' YP   YP Y8888D' Y88888P 88   YD 

------------------------------------------------------------------------

Appendix A. Installation

A.1. Requirements

   In  order  to  successfully  use the most recent Krusader, you
   need KDElibs >= 3.2.x.

   Note

        Krusader v1.01 needs KDElibs 2.x.x

        Krusader v1.02 - 1.40 needs KDElibs 3.x.x

        Krusader 1.40 prefers >= 3.2.x (otherwise not all features
        will be available)

        Krusader v1.50 needs KDElibs >= 3.2.x

   Platforms:  Linux,  FreeBSD,  Solaris(TM)  and  Mac OS 10.3
   (Panther).

   Krusader  uses  about 3-4 MByte of memory to run (and about 15
   Mbyte shared memory which is also used by more processes), but
   this may vary depending on your platform and configuration. In
   order  to  handle  archives  the  archivers must be configured
   here.

   A  package  of popular (un)packers, Krusader itself and addons
   can be found on the Krusader downloadpage.

   For  more requirements, continue to read this chapter and read
   also the FAQ section.
     _________________________________________________________

A.2. How to obtain Krusader

   The  latest  information  about  Krusader  can be found on the
   Krusader  website and Krusader project page at Sourceforge can
   be found here.
     _________________________________________________________

A.2.1. Download Krusader

   The  latest  version can be found on the Krusader downloadpage
   and  on  the  Sourceforge  mirrors.  It  contains  the  source
   tarballs  and RPM packages to whatever distro we are currently
   using.

     * Often   Mandrake(TM),   Feodora   and   SuSE  RPM's  are
       available,  sent in by Krusader users. There might be some
       other  packages  on our website, but that depends on other
       users contributions.
     * Debian  DEB  packages  and  a  DEB  packages overview are
       available.
     * There is a FreeBSD port thanks to Heiner Eichmann .
     * There  is a Mac OS-x 10.3 (Panther) port with the kdelibs
       (3.1.4) and fink.sourceforge.net thanks to Jonas Ba�r .
     * Gentoo Ebuild is available.
     * You  may  also  find  packages on Linux software archives
       such as freshmeat.net or KDE-APPS.org.
     * If   you   can't  find  a  RPM  package  for  your  Linux
       distribution,   we   recommend   searching   for  it  with
       rpmfind.net or rpmpbone.net.

   If  you  like  Krusader  go  to  one  of  these sites and rate
   Krusader, thanks.

   If  you  still  can't  find a RPM or DEB package, please don't
   worry. We provide a very detailed installation procedure. This
   very  thorough  HowTo  shows  even  newcomers  how  to compile
   Krusader  from source, even if you've never compiled a program
   from source. Please continue to read this chapter ;)
     _________________________________________________________

A.2.2. Stable version

   krusader-x.xx.tar.gz

   Note

        Krusader is released under the GNU General Public License
        (GPL), this means that THE PROGRAM IS PROVIDED "AS IS" WITH NO
        WARRANTY OF ANY KIND, even when it is marked as a stable
        release.
     _________________________________________________________

A.2.3. Development version (beta release)

   krusader-x.xx-betax.tar.gz

   Before   every   stable   release  we  release  at  least  one
   development version, so that we can hunt down the bugs.

 Warning

         This releases are beta releases and will probably contain some
         bugs.

   Note

        If you are using a development or CVS version, it is possible
        that the latest new features are not yet in the "The Krusader
        Handbook". Please read the ChangeLog file online or in the
        Krusader sources to find out more about the latest new
        features. For a brief description of the latest new features,
        please read the CVSNEWS file online or in the Krusader
        sources. User feedback and Bug reports are always welcome!

   This version has 3 goals:

     * Apply  a feature-freeze until the stable is released, only
       bugs  will  be  fixed. New features have to wait until the
       stable is released.
     * Have  feedback  from Krusader users so that we can fix the
       bugs.
     * Give  translators the time to update the translations, for
       the  coming  stable.  Please read the Krusader translation
       HowTo
     _________________________________________________________

A.2.4. CVS builds

   krusader-cvs-yyyy-mm-dd.tar.gz

  Warning

          These builds are untested and come without any warranty. They
          may contain bugfixes, new features or new bugs!

   We  provide  daily  snapshots  of  Krusader's CVS version. For
   those  who are interested, the nightly tarball can be found on
   the  Krusader's  Cutting  Edge page. Depending on the stage of
   development,  this  version will either be stable or unstable.
   Just  before  a  stable  release,  the  CVS  version is almost
   stable.  After a stable release new features will be committed
   into  CVS, which might lead to the appearance of bugs. In some
   rare  cases,  the  build  will  even  not compile if we make a
   mistake,  in  that  case  we try to fix the mistake as soon as
   possible.

   Krusader provides 2 nightly snapshots:

    1. krusader-cvs-yyyy-mm-dd.tar.gz:  make -f Makefile.cvs must
       be run before the ./configure script is available
    2. krusader-cvs2-yyyy-mm-dd.tar.gz:   for   users   who  have
       problems  with  the  make -f Makefile.cvs command, we have
       already  done  this  for you and the ./configure script is
       included in the tarball (This tarball is a bit bigger then
       the first one).

   Checkout  from  CVS.  Krusader  can  be  checked  out  through
   anonymous  (pserver)  CVS  with the following instruction set.
   The  module  you  wish  to  check out must be specified as the
   modulename. When prompted for a password for anonymous, simply
   press the Enter key.

   Currently, there are two module options:

     * krusader_kde2:  the KDE2 branch, stable but it's basically
       v1.01 and there are no planned changes
     * krusader_kde3: the KDE3 branch, that we currently use

   To checkout Krusader from CVS:
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co
 krusader_kde3

   (note:  updates  from within the modules directory do not need
   the -d parameter)

   To  checkout  a  specific  version  of Krusader from CVS (e.g.
   Krusader-1.50) :
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co
 -rversion_1_50 krusader_kde3

   (note:  updates  from within the modules directory do not need
   the -d parameter)

   Mostly being Gentoo users ourselves, we provide a Gentoo Live
   Ebuild  for all those who want to stay on the bleeding edge of
   filemanagement  and  don't  want  to  miss  the  advantages of
   portage.  Please  take  a  look at our Krusader's Cutting Edge
   page for more installation details.

   We provide also ViewCVS to browse the CVS repository.
     _________________________________________________________

A.2.5. Older releases

   Looking  for  older  releases?  Try  the  Sourceforge  mirrors
   available from our project page.
     _________________________________________________________

A.3. Compilation and installation

A.3.1. I have downloaded the sources for Krusader. What now?

   Check the environment variables KDEDIR - QTDIR.

   In  order to compile and install Krusader on your system, type
   the following in the base directory of the Krusader package:
$ ./configure
$ make
$ su -c 'make install'

   If  you  install  a  CVS  or  beta version and if Krusader was
   previously  installed  on your computer then you should delete
   the  krusaderui.rc file in your home directory to activate the
   new menu entries $ rm ~/.kde/share/apps/krusader/krusaderui.rc
   , click here for more info.

   Since  Krusader  uses autoconf and automake you should have no
   trouble compiling it. Should you run into problems please read
   the detailed installation instructions below.
     _________________________________________________________

A.3.2. Detailed installation instructions

   The  next  section  will explain step by step in detail how to
   install  Krusader. This question has been asked many times and
   especially  users  new to Linux often have problems compiling
   software  from  source.  Therefore,  we are trying to keep the
   explanations  as  detailed as possible even if they are mostly
   not  Krusader specific. Experienced users may easily skip most
   of the steps.

   If  you  encounter  problems  installing Krusader, please read
   this  installation  procedure  first and then the FAQ, if this
   does not solve the problem then feel free to ask for help with
   an help request.

    1. Open your favourite terminal emulator (e.g. Konsole).
    2. We  recommend  you create a separate directory to keep all
       the  sources  you  compile in. This will give you a better
       overview  of  installed  programs  and  makes it easier to
       uninstall them later.
$ mkdir ~/source
       The  chosen  directory  is just an example, any other will
       work.
    3. Copy  the  sources  to  the  ~/source directory and unpack
       them.
$ cp /"your_dir"/krusader-x.xx.tar.gz ~/source
$ cd ~/source
$ tar -xzvf krusader-x.xx.tar.gz
    4. Optional  step:  the  tarball  is no longer needed at this
       point, you can delete it if you want.
$ rm  krusader-x.xx.tar.gz
    5. Change to the directory containing the sources.
$ cd  krusader-x.xx
    6. Check   the   environment   variables  QTDIR  and  KDEDIR.
       Krusader's  ./configure  script  needs  to  know where the
       Qt(TM) and KDE directories are.
       QTDIR  :  <path to your Qt installation> e.g. /usr/lib/qt3
       or /usr/qt3
       KDEDIR  :  <path  to  your  KDE installation> e.g. /usr or
       /opt/kde3
       Normally  your  distribution  will  set  them for you, but
       experience has shown that some don't. You can easily check
       the values with the echo command.
$ echo $QTDIR
/usr/lib/qt3
$ echo $KDEDIR
/usr
       If  both commands give an output, the enviroment variables
       are   set   (the   above   example  are  the  settings  of
       Mandrake(TM)-Linux).  In  case  you  just  receive  empty
       lines,  the variables are not set and you have to set them
       it manually. If you have no idea what to set the variables
       to, or if you want to check if the variables are correctly
       set, ask your distributor or use the find command.
$ find /usr /opt -name qtconfig -type f -perm +111
/usr/lib/qt3/bin/qtconfig
$ find  /usr /opt -name startkde -type f -perm +111
/usr/bin/startkde
       In  this  case /usr/lib/qt3 is your QTDIR and /usr is your
       KDEDIR. The installed binaries will go to /usr/bin. Now we
       will set the enviroment variables with the export command.
$ export QTDIR=<replace with your QTDIR>
$ export KDEDIR=<replace with your KDEDIR>

     Note

          These enviroment variables are only set for the lifetime of
          your current shell. When you close your terminal and open a
          new one they will be gone. Assuming Krusader is not the only
          Qt(TM)/KDE program you want to compile, we recommend to make
          these settings permanent (e.g. append both export commands to
          your /etc/profile) file.
    7. If     you    have    downloaded    a    stable    version
       "krusader-x.xx.tar.gz"      or      a     beta     version
       "krusader-x.xx-betax.tar.gz",  you  can skip this step, in
       this case the ./configure script is provided.
       If  you  have  downloaded  a  CVS build or nightly tarball
       "krusader-cvs-yyyy-mm-dd.tar.gz"",  you  will  have to run
       the following command to create the ./configure script:
$ make -f  Makefile.cvs
       If  everything  is OK you will see the following output on
       your screen:
$ make -f  Makefile.cvs
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
$

       Note

            You will need to have: autoconf 2.52, 2.53 or 2.54 and
            automake 1.6 (or higher) to run the make -f Makefile.cvs
            command

       Tip

           If you encounter problems with this command click here.
           Krusader provides 2 nightly builds (snapshots) one with a
           ./configure script and one without.
    8. Now you are ready to run the ./configure script.
$ ./configure
       This  will take about 1 minute, if everything goes well it
       will e.g. end with the following messages:
foo

Krusader Project:
-----------------
Source code location: .
C Compiler:           gcc
C Compiler flags:     -ansi -W -Wall -pedantic -Wchar-subscripts -Wshad
ow -Wpointer-arith
-Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-O2
-Wformat-security -Wmissing-format-attribute
C++ Compiler:         g++
prefix:               /usr
kde_libraries:        /usr/include
kde_includes:         /usr/lib
kde_locale:           /usr/share/locale
qt_libraries:         /usr/lib/qt3/lib
qt_includes:          /usr/lib/qt3/include
KDEDIR:               /usr
QTDIR:                /usr/lib/qt3
Install path:         /usr/bin
krusader version:     1.50
krusader binary:      /usr/bin/krusader     (after 'make install')
Thank you for using Krusader

Good - your configure finished. Start make now
bash$
       This  is  the  output  for  Mandrake(TM)-Linux 9.2, other
       distributions may give a different output.

     Tip

         At the end of the ./configure script you will find a summary
         of the most important settings, e.g. where the Krusader binary
         will be installed (after the 'make install' command).
         Usually the Krusader binary will be installed in the
         KDEDIR/bin directory. If you would prefer to install Krusader
         in a different directory, you can do this with the following
         command: ./configure --prefix=/usr/local. In this case the
         Krusader binary will be installed in the /usr/local/bin
         directory.
         This part will also display a warning if the environment
         variables KDEDIR - QTDIR are empty.
       Use  ./configure  --help  to  see more options or read the
       INSTALL file in the Krusader sources.
       If  ./configure  fails, take a look at FAQ missing libs or
       headers.
    9. Start the compilation process with the make command.
$ make
       This  will take about 10 to 40 minutes, if everything goes
       well it will e.g. end with the following messages:
foo
make[2]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD/krArc'
make[2]: Entering directory `/foo/krusader-cvs-YYYY-MM-DD'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD'
make[1]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD'
bash$
       If  ./configure  was  successful  and make failed for some
       reason,  continue to read this page. If you can't find any
       solution  for  your  problem then feel free to post a help
       request at our Krusader Forum.
   10. If nothing went wrong, you can now install Krusader.
$ su -c 'make install'
       You will be asked to enter your root password.
   11. If  you  install a CVS or beta version and if Krusader was
       previously  installed  on  your  computer  then you should
       delete  the  krusaderui.rc  file in your home directory to
       activate the new menu entries $ rm
       ~/.kde/share/apps/krusader/krusaderui.rc  , click here for
       more info.
   12. Now you can start Krusader.
   13. Optional  step:  if you want you can clean up to save some
       diskspace.  Note:  in  this  case  all  the compiled files
       created with the make command will be deleted.
$ make clean
   14. If you ever want to uninstall Krusader, just use
$ su -c 'make uninstall'
       You will be asked to enter your root password.

   If you encounter problems with installing Krusader please read
   first the FAQ. If this installation procedure and the FAQ does
   not  solve the problem, feel free to ask for help with an help
   request.
     _________________________________________________________

A.4. Starting Krusader

   Type krusader (lower case) at a command prompt. You can create
   shortcut on your desktop or create an entry in the (KDE) menu.
   Read the previous page and the FAQ if Krusader doesn't start.

   When  Krusader  is  started  from  the  command-line,  various
   options can be specified to modify its behavior.
$ krusader
WARNING: Mt.Man: Born, looking around to get familiar.
foo

   Note

        Don't worry about the messages you get in the Konsole. These
        messages are log messages that can be used for debugging
        Krusader.

   You  can  also  use Alt+F2 to open the Run Command dialog box,
   type  krusader  (lower  case)  and press Enter or click on the
   "Run" button.

   If Krusader is installed by an RPM or DEB package then usually
   Krusader   can   be   started   from   the  K  menu.  e.g.  on
   Mandrake(TM)-Linux  10.0 click on the [kmenu.png] icon button
   and choose Applications->File tools->Krusader.

   --left <path> start left panel at <path>

   --right <path> start right panel at <path>

   --profile <panel-profile> opens panel-profile <panel-profile>

   Example:
$ krusader --left=/mnt/cdrom --right=ftp://downloads@myserver.net

   The   standard   Qt(TM)   and  KDE  command-line  options  are
   available, and can be listed by entering krusader --help .

   Other command-line options:

   --help-qt
          List Qt-specific options

   --help-kde
          List KDE-specific options

   --help-all
          List all options

   --author
          Show the authors names

   -v,--version
          Show the version number

   --license
          Show license information
     _________________________________________________________

A.5. Configure Krusader

   When  you  run  Krusader  for  the  first  time  the  Krusader
   configuration  module  Konfigurator will show up and allow you
   to  configure Krusader as well as detect installed packers and
   tools. You can always run Konfigurator again from the Settings
   menu.
     _________________________________________________________

Appendix B. Configuration files

   This  appendix  gives  an  overview of the configuration files
   used by Krusader.

   krusaderui.rc

   This  file  stores  the  users  toolbar  settings and the menu
   structure. Tip: please read also the krusaderui.rc FAQ.

   Location:     $KDEDIR/share/apps/krusader/krusaderui.rc     or
   ~/.kde/share/apps/krusader/krusaderui.rc

   krusaderrc

   This file stores the Krusader configuration.

   Location: ~/.kde/share/config/krusaderrc

   The following settings are stored:

     * Advanced
     * Archives
     * Dependencies
     * General
     * HTML Settings
     * KFileDialog
     * KFileDialog Speedbar
     * KrDetailedViewLeft
     * KrDetailedViewRight
     * KrViewerWindow
     * KrViewerWindow Toolbar mainToolBar
     * Locate
     * Look&Feel
     * Open-with settings
     * Private
     * Protocols
     * RemoteMan
     * Search
     * Startup
     * Synchronize
     * SynchronizerProfile - 1

   krbookmarks.xml

   This  file  stores  the  Krusader  bookmarks and uses the XBEL
   standard standard.

   Location: ~/.kde/share/apps/krusader/krbookmarks.xml

   useractions.xml

   This   file   stores   the   UserActions   configuration.  The
   file-structure   is   documentated   in   doxygen-headers   of
   UserActionXML.

   Location: ~/.kde/share/apps/krusader/useractions.xml
     _________________________________________________________


The following text are generic installation instructions for KDE applications
(normally you will not need it). The following text is not written by us,
but is automaticly generated by Kdevelop.


Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package 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 a while.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Type `make install' to install the programs and any data files and
     documentation.

  4. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own 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 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 the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

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 gives
default 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: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--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.
