From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problem with Allegro - make does nothing
Date: 27 Dec 1999 12:05:40 -0800
Organization: InterWorld Communications
Lines: 24
Message-ID: <83vh5kqhd7.fsf@mercury.st.hmc.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991223160459 DOT 7168D-100000 AT is> <847ktl$iq9$1 AT tron DOT sci DOT fi>
NNTP-Posting-Host: mercury.st.hmc.edu
X-Trace: nntp1.interworld.net 946325182 79230 134.173.45.219 (27 Dec 1999 20:06:22 GMT)
X-Complaints-To: usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date: 27 Dec 1999 20:06:22 GMT
X-Newsreader: Gnus v5.7/Emacs 20.4
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Lasse =?iso-8859-1?Q?K=E4rkk=E4inen?= <tronic2 AT saunalahti DOT fi> writes:

> > Are you sure this is the DJGPP version of Make?  The DJGPP version never
> > says nothing, it at least should say something like "Nothing to be done
> > for `all'".  Perhaps some other make.exe is lurking on your PATH?
> 
> Thanks! 
> 
> There was a make.com in my toolz-directory .. I have no idea where it belongs..
> but I deleted it and now that problem is gone..

Ahhh...

I've had this same problem.  Apparently VMS has scripts which are
named *.com, and I had a GNU package with a VMS build script named
make.com.  So I cd into the directory and unwittingly type make, and
the results when the CPU executes the script as machine code are not
encouraging.  (I think the machine rebooted or hard-crashed or
something.)  I spent a while thinking it was a horrible bug in make!

-- 

Nate Eldredge
neldredge AT hmc DOT edu