-
Notifications
You must be signed in to change notification settings - Fork 1
/
INSTALL
53 lines (36 loc) · 1.86 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Installation Instructions v 3.03 (April 1994)
---------------------------------------------
Unix Boxes...
On a unix machine, type 'make' to compile a copy of klatt in the
current directory. 'make install' will copy the relevant files into
the required installation binary and manual page directories. These
directories are specified at the top of the makefile and can be edited
according to local site requirements.
Use 'make clean' to remove all files created during compilation and
installation. This will leave you with the original distribution.
The code uses the 'proto' macro in an attempt at portability between
ANSI and K&R style C compilers. It has successfully been compiled
using 'cc' and 'gcc' on the Sun Sparc architecture.
SGI Boxes...
A special mention for SGI users! I have been told that the "getopt" function
as supplied with the SGI machine does not return the expected value when it
has parsed all of the command line arguments. You may have to modify the
code at this point to deal with this... Or alternatively use the GNU
getopt (as detailed below)
PC Boxes...
I have compiled this code successfully under Microsoft C 7.0. I've used the
_MSC_VER flag to do some conditional compilation, which seems to be the only
way of telling that you are using the Microsoft C package.
The code should (ho ho) compile under Borland C. I would appreciate any
feedback on this, as well as attempts at compiling / using the code using
any other compiler / architecture.
For both Microsoft C and Borland C, I believe there is no "getopt" library
function. To remedy this, and to provide a consistent interface, I've
included the source for the GNU version of getopt (usual GPL applies),
this worked fine under Microsoft C.
Other Boxes and OS's
Please let me know about any problems you have, favourite bug fixes,
enhancements you'd like to see etc.
Cheers,
Jon
j.p.iles@cs.bham.ac.uk