In article <1992Nov24.124435.4294@titan.ksc.nasa.gov> rushing@titan.ksc.nasa.gov (Sam Rushing) writes:

   To compile it, I did a 'sh configure', then chose NP_LOCAL and NS_BSD in 
   options.h; followed by a 'make'.  MOO makes it through the -Wall squeaky
   clean, with two exceptions:

   1) You need to comment out a 'signal(SIGBUS)' in one file. 
   2) execution.c crashes the compiler!  This could be bad.  The error is
      something like 'bad register spilled: this could be a bug in the compiler
      or an impossible asm statement'.

   You can evade 2) by recompiling without optimization.  So sad, that one
   little blemish on an otherwise flawless beast.  Someone should try this
   with gcc-2.3.

I've already tried it with gcc-2.3.1 (ss-921113) and it does the same
thing.  I've talked to HJ and plan to submit a bug report but haven't
gotten around to it yet.

   I have not tested it with TCP.  It will probably work.  The 'local' socket
   option works fine with the 'client_bsd' program provided.

I've also already reported it to the author of LambdaMOO. He says that
the only reason TCP was not selected by 'configure' is because the
config script checks for 'telnet', which most people don't have yet.
(don't ask me for a copy, I don't have it, either :-)

However, NP_TCP/NS_BSD mode does work under linux.

both tinytalk and mud.el (which are both on parcftp.xerox.com along
with MOO) work. (I think tinytalk required minor tweaking.)

- Jerry