If you have trouble compiling, edit cxterm-5.0/cxterm/Makefile so that CC is defined to be gcc instead of cc. (Of course, make sure that this is the Makefile generated from first running cxterm-5.0/config.sh and attempting to compile.) This change will probably be necessary on a Sun, for instance. In this case you will have to run "make" by hand in the directories cxterm and utils. If you intend, after compiling, to copy the binary to another machine of the same architecture, you may also wish to add -static to the CCOPTIONS line.

On newer Sun machines, you may find a problem with the file misc.c, at line 346. A kludge fix is to simply comment-out the line. I am not aware of the implications of this, but it seems to work. I will post a better fix later on. Also on those machines, if you use gcc as your compiler, after running config.sh remove the -xF (in two separate lines) and -cg92 compiler options in cxterm/Makefile and utils/Makefile.

On DECstations, there seems to be a bug in /bin/sh. We suggest that you acquire GNU's Bourne-shell compatible bash (say, by ftp from prep.ai.mit.edu), and use it instead, changing the first lines of the various scripts in cxterm-5.0/scripts to the full path name of wherever you put bash. When you execute cxterm-5.0/config.sh, do so indirectly, as

bash config.sh

To enable full terminal privileges within kxterm, make sure to put in the -DUTMP option in cxterm-5.0/cxterm/Makefile (say in the definition of CC), and compile as root. Then after changing the name of the executable from cxterm to kxterm do

chmod u+s kxterm

chmod go+rx kxterm