3.m4 freebsd5.m4 maxion.m4 sco-uw-2.1.m4 ultrix4.m4
bsd4.4.m4 gnu.m4 mklinux.m4 sco3.2.m4 unixware7.m4
bsdi.m4 hpux10.m4 mpeix.m4 sinix.m4 unknown.m4
bsdi1.0.m4 hpux11.m4 nextstep.m4 solaris2.m4 uxpds.m4
To include support, select the file that best describes your operating system, delete the
.m4 suffix from its name, and include the resulting name in an OSTYPE declaration:
OSTYPE(`ultrix4??)
Here, support for the DEC Ultrix operating system is defined. Note that some of
these are not entirely accurate. For example, ultrix4.m4 includes support for Ultrix
versions 4.2 and 4.3, and sunos4.1.m4 includes support for SunOS versions 4.1.2,
4.1.3, and 4.1.4.
If you pick a name for which no file exists, or if you misspell the name of the file, an
error similar to the following will print:
m4: Can't open ../ostype/ultrux4.1.m4: No such file or directory
If you omit the OSTYPE declaration entirely, you will get the following error:
*** ERROR: No system type defined (use OSTYPE macro)
17.2.2.2 MAILER( ) m4 macro
Delivery agents are not automatically declared. Instead, you must specify which ones
you want to support and which ones you want to ignore. Support is included by
using the MAILER definition:
MAILER(`local??)
* We fudge for simplicity. Actually, OSTYPE can legally be preceded by VERSION (?§17.2.3.1 on page 593)
and m4 comments.
Pages:
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040