Path: utzoo!utgpu!watmath!att!occrsh!rjd
From: rjd@occrsh.ATT.COM (Randy_Davis)
Newsgroups: comp.sources.games.bugs
Subject: Re: Nethack 3.0 compile hassle
Summary: "Too many defines"????? and Memory fault after character choice
Message-ID: <824@occrsh.ATT.COM>
Date: 2 Aug 89 14:04:12 GMT
References: <217@labii.UUCP>
Reply-To: rjd@occrsh.UUCP (Randy_Davis)
Distribution: na
Organization: AT&T Network & Data Systems, OKC
Lines: 30

In article <217@labii.UUCP> shevett@labii.UUCP (Dave Shevett) writes:
|[....]
|#define STUPID		/* avoid some complicated expressions if
|#define STUPID_CPP	/* use many small functions instead of macros to
|
|Somewhere it said to define STUPID_CPP - in unixconf.h? 
|
|#define SYSV		/* define for System V */
|#define UNIXPC		/* use in addition to SYSV for AT&T 7300/3B1 */
|			/* also note that the stock cpp qualifies as a
|			   STUPID_CPP for config.h */

  I ran into something I was not expecting....  When comiling the same module
Dave had troubles with (apply.c), the make croaked with a "rm.h: Too many
defines" about 100 times followed by the same message for hack.h.  This is
on a 3B2 model 700 running 16 Meg Ram and the 4.2 C compiler and a ulimit of
2^16.  I was quite surprised to determine that the C-preprocessor on THIS
machine qualified as a "STUPID_CPP", but defining that define allowed it to
compile.

  Of course, now it is "Memory faulting" after picking the character class
whether you or it does it, so I am now putting some tracing prints in the
code so I can find the offending statements.

  Can anyone who has delt with the Memory Fault after picking the character
class save me some time on this bug?  (Email preferable for speed sake, feel
free to also post).

Randy Davis			UUCP: ...(att!)ocrjd!randy, randy@ocrjd.att.com
				      ...(att!)occrsh!rjd,  rjd@occrsh.att.com