X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/02650b7f0e3ef470a949768bdb907183da4b3beb..a2ea208d82fdd67257d16e11b93ab17a8c48d452:/djgpp/README.in?ds=inline diff --git a/djgpp/README.in b/djgpp/README.in index df657655..78c5898a 100644 --- a/djgpp/README.in +++ b/djgpp/README.in @@ -1,6 +1,6 @@ This is a port of GNU Bison @VERSION@ to MSDOS/DJGPP. -Copyright (C) 2005 Free Software Foundation, Inc. +Copyright (C) 2005, 2006 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -22,11 +22,11 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. The DJGPP port of Bison offers LFN and SFN support depending on which OS it is running. If LFN support is available or not is determinated at - run time. If LFN support is available (DOS session under Win9X), the - standard posix file name extensions will be used. These are: y.tab.c, - y.tab.c++, y.tab.h, y.output, etc. If only SFN support is available - (plain DOS), then the standard MSDOS short file names will be used. - These are: y_tab.c, y_tab.h, y.out, etc. + run time. If LFN support is available (DOS session under Win9X, Win2K, + WinXP, etc.) the standard posix file name extensions will be used. + These are: y.tab.c, y.tab.c++, y.tab.h, y.output, etc. If only SFN + support is available (plain DOS), then the standard MSDOS short file + names will be used. These are: y_tab.c, y_tab.h, y.out, etc. It should be noticed that this bison version needs the m4 program as back end to generate the parser file (y.tab.c etc.) from the skeleton files. This implies that m4 must always be installed to get bison @@ -34,7 +34,7 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. /dev/env/DJDIR/share/bison and shall not be removed. It should also be noticed that the skeleton files bison.simple and bison.hairy are no longer supported. This applies also to the environ- - ment variables BISON_HAIRY and BISON_SIMPLE. Those variables are *no* + ment variables BISON_HAIRY and BISON_SIMPLE. Those variables are *no* longer honored at all. The kind of skeleton file bison.hairy is no longer supported at all. The skeleton file bison.simple is now called yacc.c and is an m4 script. @@ -46,8 +46,13 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. This is done by forking and using pipes for the IPC. MSDOS does not support this functionality so this has been reproduced in the usual way by redirecting stdin and stdout of bison and m4 to temporary files - and processing these files in sequence. All the changes to the sources - are documented in the djgpp/diffs file. + and processing these files in sequence. + It should be noticed that due to the great amount of file names that do + not cleanly map to 8.3 file names, you will need an OS with LFN support + to configure and compile the sources. On Win98 this implies that the + generation of numeric tails for 8.3 file name aliases must be enabled + or the compilation will fail. + Please **read** the docs. @@ -91,12 +96,12 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. with the necessary mappings. So you need first to retrieve that batch file, and then invoke it to unpack the distribution. Here's how: - djtar -x -p -o bison-2.1/djgpp/djunpack.bat bison-2.1.tar.gz > djunpack.bat - djunpack bison-2.1.tar.gz + djtar -x -p -o bison-@VERSION@/djgpp/djunpack.bat bison-@VERSION@.tar.gz > djunpack.bat + djunpack bison-@VERSION@.tar.gz (The name of the distribution archive and the leading directory of the path to `djunpack.bat' in the distribution will be different for - versions of Bison other than 2.1.) + versions of Bison other than @VERSION@.) If the argument to `djunpack.bat' include leading directories, it MUST be given with the DOS-style backslashes; Unix-style forward slashes @@ -106,29 +111,26 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. `djtar' doesn't support bzip2 decompression, you need to unpack it as follows: - bnzip2 bison-2.1.tar.bz2 - djtar -x -p -o bison-2.1/djgpp/djunpack.bat bison-2.1.tar > djunpack.bat - djunpack bison-2.1.tar + bnzip2 bison-@VERSION@.tar.bz2 + djtar -x -p -o bison-@VERSION@/djgpp/djunpack.bat bison-@VERSION@.tar > djunpack.bat + djunpack bison-@VERSION@.tar 3.3.: To build the binaries you will need the following binary packages: djdev203.zip (or a later but NOT a prior version) bsh204b.zip (or a later but NOT a prior version) - gcc400b.zip, gpp400b.zip, bnu215b.zip, mak3791b.zip, - fil40b.zip, shl20jb.zip, txt20b.zip, - txi48b.zip, grep24b.zip, sed414b.zip, - m4-144b.zip. + gccNNNb.zip, gppNNN.zip, bnuNNNb.zip, makNNNb.zip, filNNNb.zip, + shlNNNb.zip, txtNNNb.zip, txiNNNb.zip, grepNNNb.zip, sedNNNb.zip, + and m4NNN.zip If you want to run the check you will need also: - dif281b.zip + difNNNb.zip - All this packages can be found in the v2gnu directory of any + 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 bsh203b.zip or later and *NOT* a prior version or + You will need bsh204b.zip or later and *NOT* a prior version or the build will fail. The same applies to djdev203.zip. Please note - that Bison requires m4-144b.zip or later to work properly. All the - other packages are the ones I have used to build the binaries - from this source. Previuos versions of this packages may do the - job as well but I have not tested this. + that Bison requires m4-144b.zip or later to work properly. 3.4.: If for some reason you want to reconfigure the package cd into the top srcdir (bison-@TREE_VERSION@) and run the following commands: @@ -167,9 +169,10 @@ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. command: make check - No test should fail. - Please note that the testsuite only works with LFN available. On plain - DOS, most of the tests will fail due to invalid DOS names. + No test should fail but the tests #131 (Doxygen Public Documentation) + and #132 (Doxygen Private Documentation) will be skipped. Please note + that the testsuite only works with LFN available. On plain DOS, most + of the tests will fail due to invalid DOS names. 3.7.: To install the binaries, header, library, catalogs, and info docs run the following command from the top srcdir: