[HOW TO INSTALL MHPOPD]


1. In machine.h, you can find the part which is commented out.
   Then you will move the "/*" on beginning of the line to the
   place before ';' after it, referring to an attached comment
   content.

   In the following OS, there is need to change nothing. If you
   force to change anything, you will fail. So, you should go
   to the next step.
	Sun	SunOS		(5.x)
	HP	HP-UX		(11.x)
	(free)	Cygwin		(1.5.x)
	(free)	Linux		(2.x)
	(free)	FreeBSD		(2.x, 3.x, 4.x, 5.x)
	(free)	NetBSD		(1.x, 2.x, 3.x)
	(free)	OpenBSD		(2.x, 3.x)
	ASCII	BSD on Windows	(1.0, 1.5)
	Apple	Mac OS X	(10.x)

   In the following OS, while it is not confirmed whether the
   program will be running normally, the codes for these OS are
   described. Then you seem to need no change.
   At least, if you can compile it with no change, it seems
   that any changes are not necessary.
	Sun	SunOS		(4.1.x)
	SONY	NEWS-OS		(3.2, 4.x, 6.x)
	SGI	IRIX		(R4.0.5, R5.x, R6.x)
	HP	HP-UX		(9.x, 10.01)
	HITACHI	HI-UX/WE2	(01-x, 02-01, 04-02)
	NEC	EWS-UX/V(Rel4.x)(R5.3, R7.1, R8.1, R9.1, R10.1, R12.3, R13.1)
	OMRON	UniOS-U		(Ver3.00)
	OMRON	UniOS-B		(2.00)
	OMRON	Luna/Mach	(2.5)
	DEC	OSF/1		(V1.2, V2.0, V3.2, V4.x, V5.x)
	DEC	ULTRIX		(V4.x)
	IBM	AIX		(3.x, 4.x)
	Apple	A/UX		(3.0)
	DG	DG/UX		(5.4)
	Fujitsu	UXP/M		(4.0, 4.1)
	Fujitsu	UXP/DS		(V10, V20)
	Mips	RISC/os		(4.x, 5.0x)
	NeXT	NEXTSTEP	(3.0)
	(free)	386BSD		(R0.1)
	BSDI	BSD/OS		(1.1, 2.x, 3.0)
	JCC	4.4BSD-Lite	(v1.0)

   In the other OS which is not listed in both these lists,
   the program which judges the OS environment is prepared,
   and you can do "make config" to build the configuration
   file.
   But, this automatic judgment is not perfect. If you can
   not compile it, you must manually edit config.h which
   is built by "make config". And you can refer TECHKNOW.eng
   for the detail of changes.

   Reversely, in the OS which is listed in either of above
   lists, don't do "make config" because "make config" may
   sometimes cause rather unsuitable result.
   Especially in Linux, it is one of the most strange OS as
   UNIX, some special codes for Linux are prepared. Since
   these codes will never be judged automatically, you must
   never do "make config" in Linux.
   When you've done "make config" accidentally, do "make
   realclean" before the next step.

2. You can change some constants defined in mhpopd.h, if you
   want. The meaning of each constant is commented in the
   source.
   If you cannot decide, there is no problem as it is.

3. do "make".
   'cc' is used as a compiler by default. If you wish to use
   another compiler, you can specify it as "make CC=gcc". In
   this example, 'gcc' is used as a compiler.
   In case of cross-compiling, "make CC=lcc80 HOSTCC=cc" can
   specify both the cross-compiler and the compiler which
   is used for local executable files generated in build
   process. In this example, 'lcc80' is used as a compiler
   and 'cc' is used as a local compiler.
   It is supposed that files are installed under '/usr/local'
   by default. You can specify the installation path as
   "make PREFIX=/usr". In this example, it is supposed that
   files are installed under '/usr'.
   You can also specify the system configuration path as
   "make CONFDIR=/usr/local/etc".

4. Confirm whether the compiled one will run with no problem.

5. You can rewrite the macros (TOPDIR etc.) in Makefile.in
   according to your environment.
   If you rewrite DEFRC at this point, you must do "make
   clean" and do "make" again. In this case, while each
   description in documentation is different from the fact,
   there is no problem in executing this program.

6. If you need, you can rewrite mhpopdrc.sam. This file will
   be installed as the configuration file /etc/mhpopdrc, in
   which configuration items are described as default. You
   can leave them as thy are, unless you need to change them.

7. do "make install".

8. If the manual is installed correctly (you can do "man mhpopd"),
   all step is over.

   Sometimes the manual is not installed correctly, for the
   reason that nroff is not support Japanese, or so. For
   example, the meaningless characters is output, or the
   man command outputs any error message.
   In this case, if you install the plain text manual, you
   can refer the manual correctly.

   You can try the following targets for make in this rotation,
   and confirm to be able to do "man fd".
	jcatman -> jcatman-b -> jcompman -> jcompman-b
   If you do "make jcatman" and can not install correctly,
   then you do "make jcatman-b" ... you will continue.

   The target with -b will install for the terminal which
   cannot interpret the backspace (^H). The target with comp
   will install the textfile after compress it.

   If your OS doesn't support locale, the Japanese manual
   sometimes overwrite the English manual. In this case, you
   can install the only English one with the following targets.
	catman -> catman-b -> compman -> compman-b
   Each target can install the manual as well as the above
   targets, except that the Japanese manual is not installed.

9. Finish.