same one. \r
\r
I've made some attempts to compile catdoc with Watcom C (16-bit),\r
-but haven't completely socceeded. If you do, let me know. \r
+but haven't completely succeeded. If you do, let me know. \r
\r
-1. With 16-bit compilier, use COMPACT memory model\r
+1. With 16-bit compiler, use COMPACT memory model\r
If you are using Turbo C make -fmakefile.tc in src directory\r
should be enough. If you have to change anything in\r
the makefile.tc, please let me know.\r
\r
2. If you are using compilier other than Turbo C /Borland C or\r
Watcom, you should take look on fileutil.c file and possible\r
- add couple of #ifdefs here. If your succed with it, send me a\r
+ add couple of #ifdefs here. If your succeed with it, send me a\r
patch (or entire modified file, if you don't know how to make\r
a good unix-like patch). \r
\r
\r
-3. With 32-bit compilier you are on your own. I don't think that\r
+3. With 32-bit compiler you are on your own. I don't think that\r
small utilities like catdoc should require extender or DPMI host,\r
so I've never tried to build 32-bit version of catdoc for DOS,\r
But if you mix buffer sizes from UNIX version and file-name\r
and unistd.h which is provided in compat directory.\r
Compile getopt.c and add it to cc.lib and put unistd.h in\r
your include directory. Later it might help you to port other\r
- unix software. With other compilier you can also make use\r
+ unix software. With other compiler you can also make use\r
of getopt.c in compat directory (which is from GNU), but I was\r
unable to make it work with Watcom 10.0\r
\r
5. It is probably good idea to link wildargs.obj (or wildargv.obj)\r
- with catdoc. I didn't do it myself becouse I use korn shell on\r
+ with catdoc. I didn't do it myself because I use korn shell on\r
machine where I've developed catdoc, so I don't need to include\r
parameter expansion in program.\r
projects / oss / catdoc.git / blobdiff