File Explorer

1  Copyright (C) 2005, 2006, 2007, 2009, 2010, 2011, 2012, 2013, 2014, 2015,2  2016, 2017, 2018, 2019, 2020 Free Software Foundation, Inc.3  4  Copying and distribution of this file, with or without modification,5  are permitted in any medium without royalty provided the copyright6  notice and this notice are preserved.7 8README:9 10This is GNU Awk 5.1.0. It is upwardly compatible with Brian Kernighan's11version of Unix awk.  It is almost completely compliant with the122018 POSIX 1003.1 standard for awk. (See the note below about POSIX.)13 14This is a major release. See NEWS and ChangeLog for details.15 16Work to be done is described briefly in the TODO file, which is available17only in the 'master' branch in the Git repo.18 19Changes in this version are summarized in the NEWS file.20 21Read the file POSIX.STD for a discussion of issues where the standard22says one thing but gawk does something different.23 24To format the documentation with TeX, use at least version 2019-09-20.2225of texinfo.tex. There is a usable copy of texinfo.tex in the doc directory.26You must also use at least version 6.7 of texindex and of makeinfo27from the texinfo-6.7 distribution.28 29INSTALLATION:30 31Check whether there is a system-specific README file for your system under32the `README_d' directory.  If there's something there that you should33have read and didn't, and you bug me about it, I'm going to yell at you.34 35See the file INSTALL for installation instructions.36 37If you don't have Bison, use the awkgram.c file here.  It was38generated with Bison, and has no proprietary code in it.  (Note that39modifying awkgram.y without Bison will be difficult, at best.  You might40want to get a copy of Bison from the FSF too.)41 42The build mechanics depend upon Bison. Also, gawk doesn't work correctly43with some versions of yacc, so just use Bison.44 45If you have an MS-DOS, MS-Windows, or OS/2 system, use the stuff in the `pc'46directory.  Similarly, there is a separate directory for VMS.47 48Appendix B of ``GAWK: Effective Awk Programming'' discusses configuration49in detail. The configuration process is based on GNU Autoconf and50Automake.51 52After successful compilation, do `make check' to run the test suite.53There should be no output from the `cmp' invocations except in the54cases where there are small differences in floating point values, and55possibly in the case of strftime.  There may be differences based on56installed (or not installed) locales and the quality of multibyte57character support on your system.58 59Several of the tests ignore errors on purpose; those are not a problem.60If there are other differences, please investigate and report the problem.61 62PRINTING THE MANUAL63 64The `doc' directory contains a recent version of texinfo.tex, which will65be necessary for printing the manual.  Use `make dvi' to get a DVI file66from the manual. In the `doc' directory, use `make postscript' to get67PostScript versions of the manual, the man page, and the reference card.68Use `make pdf' to get PDF versions of the manuals, the man page and69the reference card.70 71BUG REPORTS AND FIXES (Un*x systems):72 73Please coordinate changes through Arnold Robbins. In particular, see74the section in the manual on reporting bugs. Note that comp.lang.awk75is about the worst place to post a gawk bug report. So too is use of76a web forum such as Stack Overflow. Please, use the mechanisms outlined77in the manual.78 79Email should be sent to bug-gawk@gnu.org.  This is a separate mailing80list at GNU Central.  The advantage to using this address is that bug81reports are archived at GNU Central.82 83Arnold Robbins84 85BUG REPORTS AND FIXES, non-Unix systems:86 87MS-DOS with DJGPP:88	Juan Manuel Guerrero89	juan.guerrero@gmx.de90 91MS-Windows with MinGW:92	Eli Zaretskii93	eliz@gnu.org94 95OS/2:96	Andreas Buening97	andreas.buening@nexgo.de98 99VMS:100	John Malmberg101	wb8tyw@qsl.net102 103z/OS (OS/390) Contact:104	Daniel Richard G.105	skunk@iSKUNK.ORG106