Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!silver!creps
From: creps@silver.bacs.indiana.edu
Newsgroups: comp.sources.bugs
Subject: Re: Help compiling nethack
Message-ID: <45700008@silver>
Date: Thu, 15-Oct-87 20:03:00 EDT
Article-I.D.: silver.45700008
Posted: Thu Oct 15 20:03:00 1987
Date-Received: Sat, 17-Oct-87 10:28:18 EDT
References: <9780@brl-adm.ARPA>
Organization: Indiana University BACS, Bloomington
Lines: 15
Nf-ID: #R:brl-adm.ARPA:-978000:silver:45700008:000:881
Nf-From: silver.bacs.indiana.edu!creps    Oct 15 19:03:00 1987


   Are you sure it said "makedefs" without an extension? I checked my copy of
Makefile.tcc and all the makedefs files had an extension of .exe or .c. I
didn't use Turbo C to compile it myself, but it sounds like it might work if
you add either the .exe or .c extension to that occurence of makedefs.
  Anyway, the "don't know how to make ..." message comes up when there is a
file referenced in the makefile which does not exist in your current directory,
AND for which there are no rules listed in makefile on how to create that file.
My guess is that your makefile is referencing "makedefs" when it actually 
means "makedefs.c" or "makedefs.exe."
-	-	-	-	-	-	-	-	-
Steve Creps on the VAX 8650 running Ultrix 2.0-1 at Indiana University.
	creps@silver.bacs.indiana.edu
"Go tell your master we are on a quest for the Holy Grail!"
"Well... I dunno... I think he's already got one."