1In order to port software to a new platform:
2
3- Choose a SYSTEMTYPE name for the new system.  You must use a name
4that includes at least the major version of the operating system
5(such as SUNOS4 or LINUX2), so that different releases of the same
6system can be supported without confusion.
7
8- Add a case statement to the "makedefs" shell script in the source
9code top-level directory that recognizes the new system reliably,
10and that emits the right system-specific information.  Be sure to
11make the code robust against user PATH settings; if the system
12offers multiple UNIX flavors (e.g. BSD and SYSV) be sure to build
13for the native flavor, instead of the emulated one.
14
15- Add an "#ifdef SYSTEMTYPE" section to the central util/sys_defs.h
16include file.  You may have to invent new feature macro names.
17Please choose sensible feature macro names such as HAS_DBM or
18FIONREAD_IN_SYS_FILIO_H.
19
20I strongly recommend against using "#ifdef SYSTEMTYPE" in individual
21source files.  While this may look like the quickest solution, it
22will create a mess when newer versions of the same SYSTEMTYPE need
23to be supported.  You're likely to end up placing "#ifdef" sections
24all over the source code again.
25