1 | # |
---|
2 | # MACHINE -- operating system specific information |
---|
3 | # |
---|
4 | # $Id: MACHINES,v 1.1.1.1 1999-02-07 18:14:04 danw Exp $ |
---|
5 | # |
---|
6 | |
---|
7 | -------------------------------------- |
---|
8 | |
---|
9 | FreeBSD: |
---|
10 | OpenBSD: |
---|
11 | NetBSD: |
---|
12 | |
---|
13 | Some BSD4.4 machines have problems when running nmh's configure script. |
---|
14 | They will be unable to find the location of vi and sendmail. This is |
---|
15 | due to POSIX features (breakage?) in the shell sh. The solution is to |
---|
16 | run the configure script under the shell `bash' |
---|
17 | |
---|
18 | bash configure |
---|
19 | |
---|
20 | -------------------------------------- |
---|
21 | |
---|
22 | HPUX: |
---|
23 | |
---|
24 | Lots of problems have been reported with using HPUX `cc'. In particular, |
---|
25 | problems with `scan' giving incorrect dates (everything is 01/00). |
---|
26 | It is highly recommended that you use `gcc' instead. |
---|
27 | |
---|
28 | Also, new versions of HPUX (10.20?) will core dump in `scan' because |
---|
29 | of some workaround code in zotnet/tws/lexstring.c. This workaround is |
---|
30 | needed for older versions of HPUX, but causes problems on newer versions. |
---|
31 | The solution is the added the line |
---|
32 | |
---|
33 | #undef hpux |
---|
34 | |
---|
35 | after line 15 of the file zotnet/tws/lexstring.c. |
---|
36 | |
---|
37 | -------------------------------------- |
---|
38 | |
---|
39 | Irix (SGI): |
---|
40 | |
---|
41 | If you are compiling nmh with POP support, then the configuration |
---|
42 | process will search for (and find) the Irix version of "ruserpass". |
---|
43 | Unfortunately, this version is buggy and causes core dumps. The best |
---|
44 | bet is to use the version that comes with nmh. After running configure, |
---|
45 | edit the Makefile in the "sbr" directory, and add "ruserpass.o" to the |
---|
46 | LIBOBJS line. Then run "make" as normal. |
---|
47 | |
---|
48 | -------------------------------------- |
---|
49 | |
---|
50 | Linux: |
---|
51 | |
---|
52 | Make sure you uncomment the Linux section in the config.h file after |
---|
53 | running configure. |
---|
54 | |
---|
55 | The configuration script does a test to discover the functions |
---|
56 | sigsetjmp/siglongjmp. Since they are macros on Linux, the configuration |
---|
57 | process doesn't find them. After running configure, you should change |
---|
58 | the line in config.h to define HAVE_SIGSETJMP. |
---|
59 | |
---|
60 | For some Linux distributions, the configure script doesn't find the |
---|
61 | ndbm/gdbm library (dbm_open, dbm_close). In this case, you should try to |
---|
62 | configure nmh like this: |
---|
63 | |
---|
64 | LIBS=-lgdbm ./configure [configure options] |
---|
65 | |
---|
66 | The configuration script does a test to discover if your vi is broken |
---|
67 | (if it reports non-zero exit codes on certain pseudo-errors). This test |
---|
68 | will hang if the program `ex' on your system is a link to the vi clone |
---|
69 | `vile'. The workaround is to replace the command ex as a link to another |
---|
70 | vi clone such as nvi or elvis. |
---|
71 | |
---|
72 | -------------------------------------- |
---|
73 | |
---|
74 | SCO: |
---|
75 | |
---|
76 | Make sure you uncomment the SCO section in the config.h file after |
---|
77 | running configure. |
---|
78 | |
---|
79 | -------------------------------------- |
---|
80 | |
---|
81 | Solaris: |
---|
82 | |
---|
83 | Builds ok. |
---|
84 | |
---|
85 | -------------------------------------- |
---|
86 | |
---|
87 | SunOS 4.1.3: |
---|
88 | |
---|
89 | You can't use the C compiler that comes with SunOS 4.1.3 since |
---|
90 | it isn't ANSI C. But nmh builds just fine with gcc. |
---|
91 | |
---|
92 | -------------------------------------- |
---|