source: trunk/essentials/sys-apps/gawk/README@ 3453

Last change on this file since 3453 was 3076, checked in by bird, 18 years ago

gawk 3.1.5

File size: 3.3 KB
Line 
1README:
2
3This is GNU Awk 3.1.5. It is upwardly compatible with the Bell Labs
4research version of awk. It is almost completely compliant with the
51993 POSIX 1003.2 standard for awk. (See the note below about POSIX.)
6
7This is a bug fix release. See NEWS and ChangeLog for details.
8
9Work to be done is described briefly in the FUTURES file. Changes in this
10version are summarized in the NEWS file. Please read the LIMITATIONS file.
11
12Read the file POSIX.STD for a discussion of how the standard says
13comparisons should be done vs. how they really should be done and how
14gawk does them.
15
16To format the documentation with TeX, use at least version 2000-10-27.17
17of texinfo.tex. There is a usable copy of texinfo.tex in the doc directory.
18
19INSTALLATION:
20
21Check whether there is a system-specific README file for your system under
22the `README_d' directory. If there's something there that you should
23have read and didn't, and you bug me about it, I'm going to yell at you.
24
25See the file INSTALL for installation instructions.
26
27If you have neither bison nor yacc, use the awkgram.c file here. It was
28generated with bison, and has no proprietary code in it. (Note that
29modifying awkgram.y without bison or yacc will be difficult, at best.
30You might want to get a copy of bison from the FSF too.)
31
32If you have a Windows32, MS-DOS or OS/2 system, use the stuff in the `pc'
33directory. Similarly, there is a separate directory for VMS.
34
35Ports for the Atari and Tandem are supplied, but they are unsupported.
36Thus, their code appears in the `unsupported' directory.
37
38Appendix B of ``GAWK: Effective Awk Programming'' discusses configuration
39in detail. The configuration process is based on GNU Autoconf and
40Automake.
41
42After successful compilation, do `make check' to run the test suite.
43There should be no output from the `cmp' invocations except in the
44cases where there are small differences in floating point values, and
45possibly in the case of strftime. Several of the tests ignore errors
46on purpose; those are not a problem. If there are other differences,
47please investigate and report the problem.
48
49PRINTING THE MANUAL
50
51The `doc' directory contains a recent version of texinfo.tex, which will
52be necessary for printing the manual. Use `make dvi' to get a DVI file
53from the manual. In the `doc' directory, use `make postscript' to get
54PostScript versions of the manual, the man page, and the reference card.
55
56BUG REPORTS AND FIXES (Un*x systems):
57
58Please coordinate changes through Arnold Robbins. In particular, see
59the section in the manual on reporting bugs. Note that comp.lang.awk
60is about the worst place to post a gawk bug report. Please, use the
61mechanisms outlined in the manual.
62
63Email should be sent to bug-gawk@gnu.org. This address sends mail to
64Arnold Robbins and the general GNU utilities bug list. The advantage
65to using this address is that bug reports are archived at GNU Central.
66
67Arnold Robbins
68
69BUG REPORTS AND FIXES, non-Unix systems:
70
71Amiga:
72 Fred Fish
73 fnf@ninemoons.com
74
75Alpha/Linux:
76 Michal Jaegermann
77 michal@gortel.phys.ualberta.ca
78
79BeOS:
80 Martin Brown
81 mc@whoever.com
82
83MS-DOS:
84 Scott Deifik
85 scottd@amgen.com
86
87 Darrel Hankerson
88 hankedr@mail.auburn.edu
89
90MS-Windows:
91 Juan Grigera
92 juan@biophnet.unlp.edu.ar
93
94OS/2:
95 andreas.buening@@nexgo.de
96
97Tandem:
98 Stephen Davies
99 scldad@sdc.com.au
100
101VMS:
102 Pat Rankin
103 rankin@pactechdata.com
Note: See TracBrowser for help on using the repository browser.