Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!VLSI.CALTECH.EDU!drazen
From: drazen@VLSI.CALTECH.EDU (Drazen Borkovic)
Newsgroups: gnu.utils.bug
Subject: difference between gnu make and make
Message-ID: <9001192327.AA10200@vlsi.caltech.edu>
Date: 19 Jan 90 23:27:23 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 41

I tried sending this to <roland@wheaties.ai.mit.edu>, but the mail
bounced.


I am not quite sure which of the involved program is at fault,
but i guess you might know.

I have a Makefile containing something like:

all:
	390-latex file

390-latex is a /bin/sh script that executes latex on a remote machine
(much faster than local one). The problem i had was that although
gnumake was reporting that it passed command "390-latex file",
390-latex was behaving as it did not receive any parameters 
(i confirmed it by adding an "echo" at the beginning of 390-latex).

I tracked the problem to the first line of 390-latex: it was empty
and only the second line contained "#!/bin/sh". When this was fixed,
everything worked fine.

The thing that still bothers me is that if i used ordinary make, the
wrong 390-latex worked correctly, but with gnumake it wasn't the case.
Also, if i used ordinary (local) latex which is ordinary binary (not a
script), BOTH makes worked correctly - i.e. parameters were passed. 

I do not know if there is a difference between makes in a way they
execute individual commands, but i would be interested in what caused 
different behaviour.

SYSTEM: sun 3/60 with OS 3.5, my interactive shell was bash,
	gnumake version 3.57, 
	if you need extra data, please let me know

Thanks for listening (reading) and i hope this was not inappropriate.

Drazen Borkovic
Caltech 256-80
Pasadena CA 91125
drazen@vlsi.caltech.edu