Failure to execute 'csh'-commands from 'make'

Hokey hokey at plus5.UUCP
Thu Aug 15 07:07:55 AEST 1985


In article <5462 at fortune.UUCP> olson at fortune.UUCP (Dave Olson) writes:
>1) Setting SHELL=/bin/csh in the makefile (for 'augmented make') will
>NOT cause all shell scripts to be run by the csh.  It WILL cause
>extra overhead for sh scripts, as csh will look at the file, determine
>it doesn't start with a '#', and exec /bin/sh to run it.  For Bourne
>shell scripts that start with a '#', there are problems (which have
>been hashed out here many times ...)

>Sigh<.  I am glad the csh supplied by Fortune does this.  The one we have
is not so nice.  If one carefully reads what I said in my earlier postings
on this issue, one will see that I qualify my statements based on *my
experience with available software*.

I *never* make sweeping generalizations.

(That was the exception which proves the rule !->)

Just to show y'all, here is a makefile:
> SHELL=/bin/csh
>
> lint:
>	lint align.c
and here are the first few lines of /usr/bin/lint:
> :
> #
> #	@(#)lint.sh	1.5
> #
> # New lint shell script.  Changed to make lint(1) act as much as is possible
> # like a different version of the cc(1) command.  This includes the notion of
> # a ``lint .o'' (.ln) and incremental linting.  Thu Jan 27 10:07:15 EST 1983
> #
> TOUT=/usr/tmp/tlint.$$		# combined input for second pass
and this is what happens when I "make lint":
> 	lint align.c
> TOUT=/usr/tmp/tlint.1946: Command not found.
> HOUT=/usr/tmp/hlint.1946: Command not found.
> LDIR=/usr/lib: Command not found.
> LLDIR=/usr/lib: Command not found.
> PATH=/bin:/usr/bin: Command not found.
> CCF=-E -C -Dlint: Command not found.
> LINTF=: Command not found.
> FILES=: Command not found.
> NDOTC=: Command not found.
> LLDIR: Undefined variable.
> *** Error code 1
> 
> Stop.

So There.
-- 
Hokey           ..ihnp4!plus5!hokey
		  314-725-9492



More information about the Comp.unix mailing list