Line | |
---|
1 | The Tandem port was done on a Cyclone machine running D20.
|
---|
2 | The port is pretty clean and all facilities seem to work except for
|
---|
3 | some of the I/O piping stuff which is just too foreign a concept for
|
---|
4 | Tandem.
|
---|
5 |
|
---|
6 | Usage is as for UNIX except that D20 requires all "{" and "}" characters
|
---|
7 | to be escaped with "~" on the command line (not in script files) and the
|
---|
8 | standard Tandem syntax for "/in filename,out filename/" must be used
|
---|
9 | instead of the usual UNIX "<" and ">" for file redirection. (Redirection
|
---|
10 | options on getline, print etc are supported.)
|
---|
11 |
|
---|
12 | The -mr=val option has been "stolen" to enable Tandem users to
|
---|
13 | process fixed-length records with no "end-of-line" character. That
|
---|
14 | is, -mr=74 tells gawk to read the input file as fixed 74-byte
|
---|
15 | records.
|
---|
16 |
|
---|
17 | To build a Tandem executable from source, down-load all of the files
|
---|
18 | so that the file names on the Tandem box are, for example ARRAYC or
|
---|
19 | AWKH. That is, make all of the file names conform to the restrictions
|
---|
20 | of D20. The "totally Tandem-specific" files are in the tandem
|
---|
21 | "subvolume" and should be copied to the main src directory before
|
---|
22 | building gawk.
|
---|
23 |
|
---|
24 | The file compit can then be used to compile and bind an executable.
|
---|
25 | Sorry, no make and no autoconfig.
|
---|
26 |
|
---|
27 | This is my first UNIX port to Tandem so I may well have missed the best
|
---|
28 | way of doing things: I just desperately needed a working awk at a
|
---|
29 | Tandem shop.
|
---|
30 |
|
---|
31 | Cheers,
|
---|
32 | Stephen Davies
|
---|
33 | (scldad@sdc.com.au)
|
---|
Note:
See
TracBrowser
for help on using the repository browser.