Path: utzoo!utgpu!water!watmath!clyde!rutgers!iuvax!pur-ee!uiucdcs!bradley!bucc2!brian
From: brian@bucc2.UUCP
Newsgroups: comp.sources.bugs
Subject: Re: NetHack gives memory fault on 3B2 (
Message-ID: <24700003@bucc2>
Date: 17 Dec 87 09:38:00 GMT
References: <33@musky2.EDU>
Lines: 36
Nf-ID: #R:musky2.EDU:33:bucc2:24700003:000:1541
Nf-From: bucc2.UUCP!brian    Dec 17 03:38:00 1987


> In article <2394@killer.UUCP> billw@killer.UUCP (Bill Wisner) writes:
> >
> >Let me clarify. When I said System V machines, I meant non-3B1s. Those are
> >obviously supported; but has anybody goten it running on a 3B2? 3B5? 3B20?
> 
> I'm using an AT&T 3B2/300, and although I got NetHack to compile with few
> problems, when I run it, it gets as far as to let you choose the class of
> character you want to play.  Immediately thereafter it says 'memory fault'
> and dies.
> 
> In the Makefile (Makefile.att), the files were linked using 'ld' directly
> rather than through the default pass the C compiler makes.  Since 'ld' does
> not search the C libraries when called directly, this stage bombed out.
> To fix this, I just passed all of the .o files to the C compiler myself
> and it linked without problem.  Did they need to be linked with 'ld' directly
> for some reason?
> 
  Ahhh, yes the old Makefile.att... I was fooled by that name as well. The 
Makefile to use on the 3B systems is Makefile.unix.

  As far as your real problem, I had the exact same thing. Then I discovered
that 3B computers do not have signed characters. So in the config.h, change
	typedef char	  schar
to
	typedef short int schar

  and all your problems (or at least most of them) should disappear. 


...............................................................................

  When the going gets weird, the weird turn pro.
						       { bucs1!brian
  Brian Michael Wendt	 {uiucdcs,cepu,ihnp4}!bradley! {       brian
 						       { bucc2!brian