This is a port of GNU M4 1.4.8 to MSDOS/DJGPP.

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

        This port is based on previous port, so the DJGPP specific changes are
        almost the same than for those previous version of m4. To compile this
        port with djdev204, a copy of popen.c from the actual cvs tree has been
        taken. If you want to compile with djdev204, you will need to use
        xp-config.bat to get makefiles that use this copy of popen instead of
        the one in djdev204. Please note that the distributed source package
        has been configured for djdev203. If you use WinXP and you want to
        rebuild the binaries, you will have to reconfigure the source package
        using xp-config.bat. As usual, all the djgpp specific files (config.bat,
        xp-config.bat, readme files, etc.) are located in the /djgpp subdir.
        Due to some name clash, you will need LFN support to configure and
        compile this package. The products itselfs will work in SFN and LFN
        environments.


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

2.1.:   Copy the binary distribution into the top DJGPP installation directory
        and unzip it running *ONE* of the following commands:
          unzip32 m4-148b.zip      or
          djtarx m4-148b.zip       or
          pkunzip -d m4-148b.zip

        For futher information about GNU m4 please read the info docs and the
        NEWS file.


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

3.1.:   To build the binaries you will need the following binary packages:
          djdev203.zip (patch level 2, see the djdev203.dsm)
          bsh204b.zip, gcc343b.zip, bnu215b.zip, mak3791b.zip,
          fil41b.zip, shl2011b.zip, txt20b.zip, txi48b.zip,
          grep24b.zip, sed414b.zip and dif281b.zip.
        For the testsuite gwk314b.zip will be needed.

        All this packages can be found in the v2gnu directory of ftp.delorie.com
        and any mirror. The above cited packages are those ones I have used to
        build the binaries from this sources. Previuos versions of those packages
        may do the job as well but I have not tested this.

3.2.:   Create a temporary directory. Copy the source package: m4-148s.zip
        into the directory and unzip it runnig ONE of the following commands:
          unzip32 m4-148s.zip      or
          djtarx m4-148s.zip       or
          pkunzip -d m4-148s.zip

3.3.:   This package does not have NLS support.
        Due to difficulties with djdev204 (2004-11-25) two config.bat files are
        distributed. The normal one called:
          config.bat
        must be used to configure the sources if you are using stock djdev203.
        The second one called:
          xp-config.bat
        must be used if you are configuring the sources with djdev204. This
        batch file will include in the sources that shall be compiled, a copy
        of popen.c from the actual cvs tree of djdev204. This will allow you
        to generate a working sed binary for WinXP.
        If for some reason you want to reconfigure the package cd into the top
        srcdir (m4-1.4-8) and run the following commands:
          del djgpp\config.cache
          make distclean
          djgpp\config  or  djgpp\xp-config

        Please note that you *MUST* delete the config.cache file in the /djgpp
        subdir or you will not really reconfigure the sources because the
        configuration informations will be read from the cache file instead
        of being newly computed.
        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\m4-1.4-8\djgpp\config x:/src/gnu/m4-1.4-8
        or:
          x:\src\gnu\m4-1.4-8\djgpp\xp-config x:/src/gnu/m4-1.4-8

        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\m4-1.4-8\djgpp\config x:/src/gnu/m4-1.4-8
        or:
          x:\src\gnu\m4-1.4-8\djgpp\xp-config x:/src/gnu/m4-1.4-8

        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.ins and supply all other needed options
        to the configure script.


3.4.:   To compile the package run from the top srcdir the command:
          make

3.5.:   Now you can run the testsuite by issuing the command:
          make check
        from the top srcdir. The following tests will fail: 089.include
        and 134.sysval. These tests fail because no kill command is available.

3.6.:   To install the binary, info docs and man pages run the following command
        from the top srcdir:
          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 appropiate
        value.
        Example:
          make install prefix=z:/some/other/dir




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

Enjoy.

          Guerrero, Juan Manuel <juan.guerrero@gmx.de>
