This is a port of @PRODUCT_NAME@ @PRODUCT_VER@  to MSDOS/DJGPP.

  GNU Bool is a utility for finding files that match a boolean expression.

  The boolean operators supported are AND, OR and NOT.  Also supported is
  the NEAR operator for locating two expressions within a short distance
  from each other.



1.:     DJGPP specific changes.
        =======================

        Minor changes needed to make the testsuite run from
        a different partition than where the sources are located.

        This port has been configured using DJGPP 2.05.  It has been configured
        to be build in the /_build directory under the top srcdir.

        The port has been configured and compiled on WinXP SP3.  There is no
        guarantee that this may be possible with any other DOS-like OS.  Due
        to the use of long file names it will not be possible to configure and
        compile without LFN support.

        The port has been compiled using gcc520 and bnu225br2.

        As usual, all djgpp specific files (config.bat, diffs, README files,
        etc.) are stored in the /djgpp directory.

        For further information about @PRODUCT_NAME@ please read the info docs and NEWS file.


2.:     Installing the binary package.
        ==============================

2.1.:   Copy the binary distribution into the top DJGPP installation directory,
        just unzip it preserving the directory structure running *ONE* of the
        following commands:
          unzip32 bool@VER@b@REL@.zip      or
          djtarx bool@VER@b@REL@.zip       or
          pkunzip -d bool@VER@b@REL@.zip


3.:     Building the binaries from sources.
        ===================================

3.1.:   Create a temporary directory and copy the source package into the
        directory.  If you download the source distribution from one of the
        DJGPP sites, just unzip it preserving the directory structure
        running *ONE* of the following commands:
          unzip32 grep@VER@s@REL@.zip      or
          djtarx grep@VER@s@REL@.zip       or
          pkunzip -d grep@VER@s@REL@.zip

3.2.:   To build the binaries you will need the following binary packages:
          djdev205.zip (or a later but NOT a prior version)
          bsh205bbr3.zip (or a later but NOT a prior version)
          gccNNNb.zip, gppNNN.zip, bnuNNNb.zip, makNNNb.zip, filNNNb.zip,
          shlNNNb.zip, txtNNNb.zip, txiNNNb.zip, grepNNNb.zip, sedNNNb.zip,
          mktmpNNb.zip and gwkNNNb.zip.

        If you want to run the check you will need also:
          difNNNb.zip and mktmpNNNb.zip

        NNN represents the latest version number of the binary packages.  All
        this packages can be found in the /v2gnu directory of any
        ftp.delorie.com mirror.
        You will need bsh205bbr3.zip or later and *NOT* a prior version or
        the build will fail.  The same applies to djdev205.zip.

3.3.:   The package has been configured to be build in a separate build directory
        under the top srcdir (aka @NAME@-@DIRECTORY@).  To build the binaries cd
        into /_build directory.  If for some reason you want to reconfigure the
        package cd into the build directory and run the
        following commands:
          del config.cache
          make clean
          ..\djgpp\config ./..

        Please note that you *MUST* delete the config.cache file in the /_build
        directory or you will not really reconfigure the sources because the
        configuration informations will be read from the cache file instead
        of being newly computed.

        config.bat, among other things, will start the configure script passing
        to it a couple of arguments.  You can control these argument passing the
        following command line arguments to config.bat:
          cache or no-cache, default cache.  Cache in build directory.
          dep or no-dep, default no-dep.  No dependency tracking.
        All other configure specific options are not set by config.bat so their
        values are left as they are.  If no arguments are passed to config.bat
        then the default values are used.


        To build the programs in a directory other than where the sources are,
        you must add the parameter that specifies the source directory,
        e.g:
          x:\src\gnu\@NAME@-@DIRECTORY@\djgpp\config x:/src/gnu/@NAME@-@DIRECTORY@

        Lets assume you want to build the binaries in a directory placed on a
        different drive (z:\build in this case) from where the sources are,
        then you will run the following commands:
          z:
          md \build
          cd \build
          x:\src\gnu\@NAME@-@DIRECTORY@\djgpp\config x:/src/gnu/@NAME@-@DIRECTORY@

        The order of the options and the srcdir option does not matter.  You
        *MUST* use forward slashes to specify the source directory.

        The batch file will set same environment variables, make MSDOS specific
        modifications to the Makefile.in's and supply all other needed options
        to the configure script.

3.4.:   To compile the package run from the directory where you have configured
        the sources the command:
          make

3.5.:   Now you can run the tests if you like.  Start the command:
          make check

3.6.:   To install the binaries and info docs run the following command from
        the directory where you have configured the sources:
          make install

        This will install the products into your DJGPP installation tree given
        by the default prefix "/dev/env/DJDIR".  If you prefer to install them
        into some other directory you will have to set prefix to the appropriate
        value:
          make install prefix=z:/some/other/place



        Send bool specific bug reports to <bug-bool@gnu.org>.
        Send suggestions and bug reports concerning the DJGPP port
        to comp.os.msdos.djgpp or <djgpp@delorie.com>.

Enjoy.

          Guerrero, Juan Manuel <st001906@hrz1.hrz.tu-darmstadt.de>
