1
2Notes on building SpamAssassin on VMS
3-------------------------------------
4
5  - Firstly, do not do a default build; this will build a set of C components
6    which currently use Autoconf to determine their dependencies, to build
7    "spamc".
8
9    Instead, run
10
11        perl Makefile.PL
12        make spamassassin
13
14    If you want "spamc" I suggest you provide a replacement header and
15    binaries.mk we can use, then we can special-case VMS in Makefile.PL to use
16    those instead of running autoconf.
17
18  - The generated Makefile.PL no longer relies on UNIX input/output
19    redirection; /bin/sh "for" loops; @foo "silent" directives; backslashed
20    continuations; or [ -f foo ] || somecommand conditionals.  At least, not in
21    our code any more ;)
22
23  - There are still some UNIX paths inside the generated Makefile:
24    "rules/local.cf" for example.  Suggestions on how to work around this
25    neatly inside the Makefile syntax while gaining VMS compatibility would be
26    welcome!
27
28  - "make test" will probably rely heavily on UNIX-style input and output
29    redirection, so will probably still fail.
30
31  - bug 1099 in the SA Bugzilla is being used to track progress.
32
33        http://issues.apache.org/SpamAssassin/show_bug.cgi?id=1099
34
35
36