aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/ChangeLog4
-rw-r--r--doc/gawk.info114
-rw-r--r--doc/gawk.texi21
3 files changed, 67 insertions, 72 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 7dea18a2..12a4de21 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+Thu Feb 10 21:31:36 2011 Andreas Buening <andreas.buening@nexgo.de>
+
+ * gawk.texi: Update OS/2 information.
+
Thu Feb 10 21:06:14 2011 Arnold D. Robbins <arnold@skeeve.com>
* lflashlight-small.xpic: Renamed from lflashlight.small.xpic.
diff --git a/doc/gawk.info b/doc/gawk.info
index aa1d9ab2..51f91d5d 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -20317,6 +20317,7 @@ needed for the build may be found at
MS-Windows binary of `gawk', type `make mingw32'.
The 32 bit EMX version of `gawk' works "out of the box" under OS/2.
+However, it is highly recommended to use GCC 2.95.3 for the compilation.
In principle, it is possible to compile `gawk' the following way:
$ ./configure
@@ -20325,23 +20326,17 @@ In principle, it is possible to compile `gawk' the following way:
This is not recommended, though. To get an OMF executable you should
use the following commands at your `sh' prompt:
- $ CPPFLAGS="-D__ST_MT_ERRNO__"
- $ export CPPFLAGS
$ CFLAGS="-O2 -Zomf -Zmt"
$ export CFLAGS
$ LDFLAGS="-s -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio -Zstack 0x6000"
$ export LDFLAGS
$ RANLIB="echo"
$ export RANLIB
- $ ./configure --prefix=c:/usr --without-included-gettext
+ $ ./configure --prefix=c:/usr
$ make AR=emxomfar
- These are just suggestions. You may use any other set of
-(self-consistent) environment variables and compiler flags.
-
- To get an FHS-compliant file hierarchy it is recommended to use the
-additional `configure' options `--infodir=c:/usr/share/info',
-`--mandir=c:/usr/share/man' and `--libexecdir=c:/usr/lib'.
+ These are just suggestions for use with GCC 2.x. You may use any
+other set of (self-consistent) environment variables and compiler flags.
If you use GCC 2.95 it is recommended to use also:
@@ -20350,8 +20345,6 @@ additional `configure' options `--infodir=c:/usr/share/info',
You can also get an `a.out' executable if you prefer:
- $ CPPFLAGS="-D__ST_MT_ERRNO__"
- $ export CPPFLAGS
$ CFLAGS="-O2 -Zmt"
$ export CFLAGS
$ LDFLAGS="-s -Zstack 0x6000"
@@ -20360,12 +20353,12 @@ additional `configure' options `--infodir=c:/usr/share/info',
$ ./configure --prefix=c:/usr
$ make
- NOTE: Versions later than GCC 2.95, i.e., GCC 3.x using the
- Innotek libc were not tested.
+ NOTE: Compilation of `a.out' executables also works with GCC 3.2.
+ Versions later than GCC 3.2 have not been tested successfully.
`make install' works as expected with the EMX build.
- NOTE: Most OS/2 ports of GNU `make' are not able to handle the
+ NOTE: Ancient OS/2 ports of GNU `make' are not able to handle the
Makefiles of this package. If you encounter any problems with
`make', try GNU Make 3.79.1 or later versions. You should find
the latest version on `ftp://hobbes.nmsu.edu/pub/os2/'.
@@ -25012,8 +25005,7 @@ Index
* compiling gawk for Cygwin: Cygwin. (line 6)
* compiling gawk for MS-DOS and MS-Windows: PC Compiling. (line 13)
* compiling gawk for VMS: VMS Compilation. (line 6)
-* compiling gawk with EMX for OS/2 and MS-Windows: PC Compiling.
- (line 28)
+* compiling gawk with EMX for OS/2: PC Compiling. (line 28)
* compl() function (gawk): Bitwise Functions. (line 42)
* complement, bitwise: Bitwise Functions. (line 25)
* compound statements, control statements and: Statements. (line 10)
@@ -27448,50 +27440,50 @@ Node: Non-Unix Installation807700
Node: PC Installation808158
Node: PC Binary Installation809457
Node: PC Compiling811305
-Node: PC Testing814451
-Node: PC Using815627
-Node: Cygwin819812
-Node: MSYS820809
-Node: VMS Installation821323
-Node: VMS Compilation821927
-Node: VMS Installation Details823504
-Node: VMS Running825134
-Node: VMS POSIX826731
-Node: VMS Old Gawk828029
-Node: Bugs828501
-Node: Other Versions832366
-Node: Notes837645
-Node: Compatibility Mode838337
-Node: Additions839120
-Node: Accessing The Source839932
-Node: Adding Code841355
-Node: New Ports846903
-Node: Dynamic Extensions851016
-Node: Internals852392
-Node: Plugin License861508
-Node: Sample Library862142
-Node: Internal File Description862828
-Node: Internal File Ops866535
-Ref: Internal File Ops-Footnote-1871303
-Node: Using Internal File Ops871451
-Node: Future Extensions873828
-Node: Basic Concepts876332
-Node: Basic High Level877089
-Ref: Basic High Level-Footnote-1881124
-Node: Basic Data Typing881309
-Node: Floating Point Issues885834
-Node: String Conversion Precision886917
-Ref: String Conversion Precision-Footnote-1888611
-Node: Unexpected Results888720
-Node: POSIX Floating Point Problems890546
-Ref: POSIX Floating Point Problems-Footnote-1894242
-Node: Glossary894280
-Node: Copying918379
-Node: GNU Free Documentation License955936
-Node: next-edition981080
-Node: unresolved981432
-Node: revision981932
-Node: consistency982355
-Node: Index985854
+Node: PC Testing814249
+Node: PC Using815425
+Node: Cygwin819610
+Node: MSYS820607
+Node: VMS Installation821121
+Node: VMS Compilation821725
+Node: VMS Installation Details823302
+Node: VMS Running824932
+Node: VMS POSIX826529
+Node: VMS Old Gawk827827
+Node: Bugs828299
+Node: Other Versions832164
+Node: Notes837443
+Node: Compatibility Mode838135
+Node: Additions838918
+Node: Accessing The Source839730
+Node: Adding Code841153
+Node: New Ports846701
+Node: Dynamic Extensions850814
+Node: Internals852190
+Node: Plugin License861306
+Node: Sample Library861940
+Node: Internal File Description862626
+Node: Internal File Ops866333
+Ref: Internal File Ops-Footnote-1871101
+Node: Using Internal File Ops871249
+Node: Future Extensions873626
+Node: Basic Concepts876130
+Node: Basic High Level876887
+Ref: Basic High Level-Footnote-1880922
+Node: Basic Data Typing881107
+Node: Floating Point Issues885632
+Node: String Conversion Precision886715
+Ref: String Conversion Precision-Footnote-1888409
+Node: Unexpected Results888518
+Node: POSIX Floating Point Problems890344
+Ref: POSIX Floating Point Problems-Footnote-1894040
+Node: Glossary894078
+Node: Copying918177
+Node: GNU Free Documentation License955734
+Node: next-edition980878
+Node: unresolved981230
+Node: revision981730
+Node: consistency982153
+Node: Index985652

End Tag Table
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 6a7822b6..4b8fc19a 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -27317,8 +27317,9 @@ build @command{gawk} using the DJGPP tools, enter @samp{make djgpp}.
@uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}.) To build a
native MS-Windows binary of @command{gawk}, type @samp{make mingw32}.
-@cindex compiling @command{gawk} with EMX for OS/2 and MS-Windows
+@cindex compiling @command{gawk} with EMX for OS/2
The 32 bit EMX version of @command{gawk} works ``out of the box'' under OS/2.
+However, it is highly recommended to use GCC 2.95.3 for the compilation.
In principle, it is possible to compile @command{gawk} the following way:
@example
@@ -27330,24 +27331,24 @@ This is not recommended, though. To get an OMF executable you should
use the following commands at your @command{sh} prompt:
@example
-$ @kbd{CPPFLAGS="-D__ST_MT_ERRNO__"}
-$ @kbd{export CPPFLAGS}
$ @kbd{CFLAGS="-O2 -Zomf -Zmt"}
$ @kbd{export CFLAGS}
$ @kbd{LDFLAGS="-s -Zcrtdll -Zlinker /exepack:2 -Zlinker /pm:vio -Zstack 0x6000"}
$ @kbd{export LDFLAGS}
$ @kbd{RANLIB="echo"}
$ @kbd{export RANLIB}
-$ @kbd{./configure --prefix=c:/usr --without-included-gettext}
+$ @kbd{./configure --prefix=c:/usr}
$ @kbd{make AR=emxomfar}
@end example
-These are just suggestions. You may use any other set of (self-consistent)
-environment variables and compiler flags.
+These are just suggestions for use with GCC 2.x. You may use any other set of
+(self-consistent) environment variables and compiler flags.
+@ignore
To get an FHS-compliant file hierarchy it is recommended to use the additional
@command{configure} options @option{--infodir=c:/usr/share/info}, @option{--mandir=c:/usr/share/man}
and @option{--libexecdir=c:/usr/lib}.
+@end ignore
@ignore
The internal @code{gettext} library tends to be problematic. It is therefore recommended
@@ -27365,8 +27366,6 @@ $ @kbd{export LIBS}
You can also get an @code{a.out} executable if you prefer:
@example
-$ @kbd{CPPFLAGS="-D__ST_MT_ERRNO__"}
-$ @kbd{export CPPFLAGS}
$ @kbd{CFLAGS="-O2 -Zmt"}
$ @kbd{export CFLAGS}
$ @kbd{LDFLAGS="-s -Zstack 0x6000"}
@@ -27378,14 +27377,14 @@ $ @kbd{make}
@end example
@quotation NOTE
-Versions later than GCC 2.95, i.e., GCC 3.x using the Innotek libc
-were not tested.
+Compilation of @code{a.out} executables also works with GCC 3.2.
+Versions later than GCC 3.2 have not been tested successfully.
@end quotation
@samp{make install} works as expected with the EMX build.
@quotation NOTE
-Most OS/2 ports of GNU @command{make} are not able to handle
+Ancient OS/2 ports of GNU @command{make} are not able to handle
the Makefiles of this package. If you encounter any problems with
@command{make}, try GNU Make 3.79.1 or later versions. You should
find the latest version on