Convert whatnow over to using the new Attach header.

[nmh] / MACHINES

diff --git a/MACHINES b/MACHINES
index 450662018589cebe307c4fdd3931e3de9ba7b6cf..216a6ab41d83d36f1b45f4768cda09a5943425fc 100644 (file)
--- a/MACHINES
+++ b/MACHINES
@@ -1,12 +1,12 @@
 #
 #

-# MACHINE -- operating system specific information
+# MACHINES -- operating system specific information

 #
 
 nmh is known to compile on the following platforms (save the
 exceptions noted below), using an ANSI C compiler, such as gcc.
 
 AIX 4.1.5.0.01
 #
 
 nmh is known to compile on the following platforms (save the
 exceptions noted below), using an ANSI C compiler, such as gcc.
 
 AIX 4.1.5.0.01

-Cygwin (setup version 2.763, other versions may be fine)
+Cygwin (setup version 2.831, other versions may be fine)

 FreeBSD
 IRIX 6.5
 Linux 2.2 to current (glibc 2.1 to current)
 FreeBSD
 IRIX 6.5
 Linux 2.2 to current (glibc 2.1 to current)


@@ -18,34 +18,33 @@ SunOS 4.1
 
 Known Compilation problems:
 --------------------------------------
 
 Known Compilation problems:
 --------------------------------------

-FreeBSD:
-OpenBSD:
-NetBSD:
-
-Some BSD4.4 machines have problems when running nmh's configure script.
-They will be unable to find the location of vi and sendmail.  This is
-due to POSIX features (breakage?) in the shell sh.  The solution is to
-run the configure script under the shell `bash':
+Cygwin:

 
 

-    % bash configure
+Be sure to install these Cygwin packages (or later versions):
+  libdb4.8
+  libdb4.8-devel
+  libgdbm-devel
+  libncurses-devel

 
 

---------------------------------------
-Mac OS X/Rhapsody 5:
+Some versions of libncurses-devel do not install /usr/include/curses.h,
+/usr/include/term.h, and /usr/include/termcap.h.  If yours does not,
+add /usr/include/ symlinks to those files in /usr/include/ncurses/.

 
 

-Version 5.3 at least has the same sh/bash bug as the *BSD systems
-above. This appears to be fixed in 5.5.
+The database packages are only used by slocal(1).

 
 

-Will not compile correctly unless you configure with the --enable-debug
-option. It appears to find conflicts in the headers only when debugging
-is disabled. With debugging enabled, it compiles and runs happily.
+If configuring with --with-cyrus-sasl, install these Cygwin packages:
+  libsasl2
+  libsasl2-devel

 
 

---------------------------------------
-Cygwin:
+If configuring with --with-tls, install this Cygwin package (or a
+later version):
+  libgnutls28

 
 

-Be sure to install Cygwin packages libncurses-devel and libncurses10,
-in the Libs category.
+When running the nmh test suite ("make check"), it helps to have
+/usr/bin/ ahead of any Windows directories on your PATH.

 
 

-The few minor compile warnings can be ignored.
+Note that the -link switch to refile cannot be used on FAT32 and
+similar filesystems.

 
 --------------------------------------
 HPUX:
 
 --------------------------------------
 HPUX:


@@ -74,11 +73,19 @@ use GNU make instead of Irix make.)
 --------------------------------------
 Linux:
 
 --------------------------------------
 Linux:
 

-The configuration script does a test to discover if your vi is broken
-(if it reports non-zero exit codes on certain pseudo-errors).  This test
-will hang if the program `ex' on your system is a link to the vi clone
-`vile'.  The workaround is to replace the command ex as a link to another
-vi clone such as nvi or elvis.
+These packages are required at runtime:
+  ncurses-libs
+  libdb (only for slocal(1))
+  cyrus-sasl-lib (if configured with --with-cyrus-sasl)
+  gnutls (if configured with --with-tls)
+
+For building, these packages are required:
+  ncurses-devel
+  libdb-devel (only for slocal(1))
+  gdbm-devel (only for slocal(1))
+
+If configuring with --with-cyrus-sasl, install these packages:
+  cyrus-sasl-lib-devel

 
 --------------------------------------
 Solaris:
 
 --------------------------------------
 Solaris:


@@ -95,12 +102,14 @@ a better solution. The whole thing is probablly going to be chucked
 with UTF-8 support anyway.
 
 Other than the warnings, it builds ok.
 with UTF-8 support anyway.
 
 Other than the warnings, it builds ok.

+

 --------------------------------------
 SunOS 4.1.1/4.1.3/4.1.4:
 
 You can't use the C compiler that comes with SunOS 4 since
 it isn't ANSI C.  But nmh builds just fine with gcc. With
 --enable-debug you will see a lot of warnings.
 --------------------------------------
 SunOS 4.1.1/4.1.3/4.1.4:
 
 You can't use the C compiler that comes with SunOS 4 since
 it isn't ANSI C.  But nmh builds just fine with gcc. With
 --enable-debug you will see a lot of warnings.

+

 --------------------------------------
 
 --
 --------------------------------------
 
 --